docs: change notes across docs based on redesign (#8662)
Change the prerequisites / soon / other notes based on latest redesign Depends on #8661
This commit is contained in:
1 parent
320b01f45d
commit
b23f0f8188
41 files changed
+291
-220
No files matched your search
@@ -5,9 +5,3 @@ export const metadata = {
|
||||
# {metadata.title}
|
||||
|
||||
In the next chapters, you'll learn more about creating data models, including property types, relationships, and more.
|
||||
|
||||
<Note type="soon" title="Important">
|
||||
|
||||
Data models are in active development and may change.
|
||||
|
||||
</Note>
|
||||
@@ -1,26 +1,22 @@
|
||||
import { BetaBadge } from "docs-ui"
|
||||
|
||||
export const metadata = {
|
||||
title: `${pageNumber} Data Model Relationships`,
|
||||
}
|
||||
|
||||
# {metadata.title}
|
||||
# {metadata.title} <BetaBadge text="Beta" tooltipText="Data model relationships are in active development and may change." />
|
||||
|
||||
In this chapter, you’ll learn how to define relationships between data models in your module.
|
||||
|
||||
<Note type="soon" title="Important">
|
||||
|
||||
Data model relationships are in active development and may change.
|
||||
|
||||
</Note>
|
||||
|
||||
<Note title="Use data model relationships when" type="success">
|
||||
|
||||
- You want to create a relation between data models in the same module.
|
||||
You want to create a relation between data models in the same module.
|
||||
|
||||
</Note>
|
||||
|
||||
<Note title="Don't use data model relationships if" type="error">
|
||||
|
||||
- You want to create a relationship between data models in different modules. Use module links instead.
|
||||
You want to create a relationship between data models in different modules. Use module links instead.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -1,17 +1,13 @@
|
||||
import { BetaBadge } from "docs-ui"
|
||||
|
||||
export const metadata = {
|
||||
title: `${pageNumber} Module Link`,
|
||||
}
|
||||
|
||||
# {metadata.title}
|
||||
# {metadata.title} <BetaBadge text="Beta" tooltipText="Module links are in active development." />
|
||||
|
||||
In this chapter, you’ll learn what a module link is.
|
||||
|
||||
<Note type="soon" title="In Development">
|
||||
|
||||
Module links are in active development.
|
||||
|
||||
</Note>
|
||||
|
||||
## What is a Module Link?
|
||||
|
||||
A module link forms an association between two data models of different modules, while maintaining module isolation.
|
||||
@@ -20,13 +16,13 @@ You can then retrieve data across the linked modules, and manage their linked re
|
||||
|
||||
<Note title="Use module links when" type="success">
|
||||
|
||||
- You want to create a relation between data models from different modules.
|
||||
You want to create a relation between data models from different modules.
|
||||
|
||||
</Note>
|
||||
|
||||
<Note title="Don't use module links if" type="error">
|
||||
|
||||
- You want to create a relationship between data models in the same module. Use data model relationships instead.
|
||||
You want to create a relationship between data models in the same module. Use data model relationships instead.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -1,17 +1,13 @@
|
||||
import { BetaBadge } from "docs-ui"
|
||||
|
||||
export const metadata = {
|
||||
title: `${pageNumber} Remote Link`,
|
||||
}
|
||||
|
||||
# {metadata.title}
|
||||
# {metadata.title} <BetaBadge text="Beta" tooltipText="Remote Links are in active development." />
|
||||
|
||||
In this chapter, you’ll learn what the remote link is and how to use it to manage links.
|
||||
|
||||
<Note type="soon" title="In Development">
|
||||
|
||||
Remote Links are in active development.
|
||||
|
||||
</Note>
|
||||
|
||||
## What is the Remote Link?
|
||||
|
||||
The remote link is a class with utility methods to manage links between data models. It’s registered in the Medusa container under the `remoteLink` registration name.
|
||||
|
||||
@@ -16,7 +16,7 @@ The service factory generates data management methods for your data models, so y
|
||||
|
||||
<Note title="Extend the service factory when" type="success">
|
||||
|
||||
- Your service provides data-management functionalities of your data models.
|
||||
Your service provides data-management functionalities of your data models.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -8,13 +8,13 @@ In this chapter, you'll learn how to expose a hook in your workflow.
|
||||
|
||||
<Note title="Expose workflow hooks when" type="success">
|
||||
|
||||
- Your workflow is reusable in other applications, and you allow performing an external action at some point in your workflow.
|
||||
Your workflow is reusable in other applications, and you allow performing an external action at some point in your workflow.
|
||||
|
||||
</Note>
|
||||
|
||||
<Note title="Don't expose workflow hooks if" type="error">
|
||||
|
||||
- Your workflow isn't reusable by other applications. Use a step that performs what a hook handler would instead.
|
||||
Your workflow isn't reusable by other applications. Use a step that performs what a hook handler would instead.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ Medusa exposes hooks in many of its workflows that are used in its API routes. Y
|
||||
|
||||
<Note title="Consume workflow hooks when" type="success">
|
||||
|
||||
- You want to perform a custom action during a workflow's execution, such as when a product is created.
|
||||
You want to perform a custom action during a workflow's execution, such as when a product is created.
|
||||
|
||||
</Note>
|
||||
|
||||
|
||||
Reference in new issue
Block a user