docs: fix note about how method names are generated (#8240)
* docs: fix note about how method names are generated * small fix
This commit is contained in:
1 parent
bcba5b3a6c
commit
97f64a5cfe
1 file changed
+3
-3
@@ -56,9 +56,9 @@ In the example above, since the `HelloModuleService` extends `MedusaService`, it
|
|||||||
|
|
||||||
The service factory generates data-management methods for each of the data models provided in the first parameter.
|
The service factory generates data-management methods for each of the data models provided in the first parameter.
|
||||||
|
|
||||||
The method's names are the operation's name, suffixed by the data model's name.
|
The method's names are the operation's name, suffixed by the data model's key in the object parameter passed to `MedusaService`.
|
||||||
|
|
||||||
For example, the following methods are generated for the code snippet above:
|
For example, the following methods are generated for the service above:
|
||||||
|
|
||||||
<Tabs defaultValue="listMyCustoms" layoutType="vertical" className="mt-2">
|
<Tabs defaultValue="listMyCustoms" layoutType="vertical" className="mt-2">
|
||||||
<TabsList>
|
<TabsList>
|
||||||
@@ -290,4 +290,4 @@ class HelloModuleService extends MedusaService({
|
|||||||
}
|
}
|
||||||
|
|
||||||
export default HelloModuleService
|
export default HelloModuleService
|
||||||
```
|
```
|
||||||
Reference in new issue
Block a user