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

docs: use tooling convention across docs (#10512)

Browse Source
This commit is contained in:
Shahed Nasser authored and GitHub committed 2024-12-09 19:15:29 +02:00
1 parent 7c76ee24cb
commit 3409953c4f
76 files changed
+283 -265
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

www/apps/resources/app/commerce-modules/auth/create-actor-type/page.mdx
+1 -1
View File
@@ -112,7 +112,7 @@ This workflow accepts the manager’s data and the associated auth identity’s
The workflow has two steps:
1. Create the manager using the `createManagerStep`.
2. Set the `app_metadata` property of the associated auth identity using the `setAuthAppMetadataStep` step imported from `@medusajs/medusa/core-flows`. You specify the actor type `manager` in the `actorType` property of the step’s input.
2. Set the `app_metadata` property of the associated auth identity using the `setAuthAppMetadataStep` from Medusa's core workflows. You specify the actor type `manager` in the `actorType` property of the step’s input.
---
www/apps/resources/app/commerce-modules/auth/page.mdx
+1 -1
View File
@@ -10,7 +10,7 @@ The Auth Module provides authentication-related features in your Medusa and Node
## How to Use Auth Module's Service
Use the Auth Module's main service by resolving from the Medusa container the resource `Modules.AUTH` imported from `@medusajs/framework/utils`.
Use the Auth Module's main service by resolving from the Medusa container the resource `Modules.AUTH`.
For example: