asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: capitalize use of Framework across docs (#12207)

Browse Source 
* docs: capitalize use of Framework across docs

* generate llm
This commit is contained in:
Shahed Nasser
2025-04-17 10:40:26 +03:00
committed by GitHub
parent f6b20a943e
commit 42262d41a1
36 changed files with 14297 additions and 14283 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/book/app/learn/customization/extend-features/extend-create-product/page.mdx
+1 -1
View File
@@ -87,7 +87,7 @@ createProductsWorkflow.hooks.productsCreated(
Workflows have a special `hooks` property to access its hooks and consume them. Each hook, such as `productsCreated`, accepts a step function as a parameter. The step function accepts the following parameters:
1. An object having an `additional_data` property, which is the custom data passed in the request body under `additional_data`. The object will also have properties passed from the workflow to the hook, which in this case is the `products` property that holds an array of the created products.
2. An object of properties related to the step's context. It has a `container` property whose value is the [Medusa container](../../../fundamentals/medusa-container/page.mdx) to resolve framework and commerce tools.
2. An object of properties related to the step's context. It has a `container` property whose value is the [Medusa container](../../../fundamentals/medusa-container/page.mdx) to resolve Framework and commerce tools.
In the step, if a brand ID is passed in `additional_data`, you resolve the Brand Module's service and use its generated `retrieveBrand` method to retrieve the brand by its ID. The `retrieveBrand` method will throw an error if the brand doesn't exist.
www/apps/book/app/learn/customization/extend-features/page.mdx
+1 -1
View File
@@ -8,7 +8,7 @@ In the upcoming chapters, you'll learn about the concepts and tools to extend Me
In other commerce platforms, you extend core features and models through hacky workarounds that can introduce unexpected issues and side effects across the platform. It also makes your application difficult to maintain and upgrade in the long run.
Medusa's framework and orchestration tools mitigate these issues while supporting all your customization needs:
The Medusa Framework and orchestration tools mitigate these issues while supporting all your customization needs:
- [Module Links](../../fundamentals/module-links/page.mdx): Link data models of different modules without building direct dependencies, ensuring that the Medusa application integrates your modules without side effects.
- [Workflow Hooks](../../fundamentals/workflows/workflow-hooks/page.mdx): inject custom functionalities into a workflow at predefined points, called hooks. This allows you to perform custom actions as a part of a core workflow without hacky workarounds.