chore(docs): Generated References (automated) (#9727)

Generated the following references:
- `api_key`
- `auth`
- `cart`
- `core_flows`
- `currency`
- `customer`
- `dml`
- `fulfillment`
- `helper_steps`
- `inventory_next`
- `js_sdk`
- `medusa`
- `medusa_config`
- `modules`
- `modules_sdk`
- `notification`
- `order`
- `order_models`
- `payment`
- `pricing`
- `product`
- `promotion`
- `region`
- `sales_channel`
- `stock_location_next`
- `store`
- `tax`
- `tax_provider`
- `types`
- `user`
- `utils`
- `workflows`

Co-authored-by: Oli Juhl <59018053+olivermrbl@users.noreply.github.com>
Co-authored-by: Shahed Nasser <27354907+shahednasser@users.noreply.github.com>
This commit is contained in:
authored and GitHub committed 2024-10-24 09:41:14 +00:00
1 parent e196ad7659
commit 5deeae060a
2313 files changed
+533036 -383477

No files matched your search

@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `createSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
## createSalesChannels(data, sharedContext?): Promise&#60;[SalesChannelDTO](../../../interfaces/sales_channel.SalesChannelDTO/page.mdx)[]&#62;
This method creates sales channels.
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `deleteSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
## deleteSalesChannels(ids, sharedContext?): Promise&#60;void&#62;
This method deletes sales channel by their IDs.
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `listAndCountSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
This method retrieves a paginated list of sales channels along with the total count of available sales channels satisfying the provided filters.
## Example
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `listSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
This method retrieves a paginated list of sales channels based on optional filters and configuration.
## Example
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `restoreSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
This method restores a soft deleted sales channel by its IDs.
## Example
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `retrieveSalesChannel` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
This method retrieves a sales channel by its ID.
## Example
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `softDeleteSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
This method soft deletes sales channels by their IDs.
## Example
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `updateSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
## updateSalesChannels(channelId, data, sharedContext?): Promise&#60;[SalesChannelDTO](../../../interfaces/sales_channel.SalesChannelDTO/page.mdx)&#62;
This method updates an existing sales channel.
@@ -10,6 +10,12 @@ import { TypeList } from "docs-ui"
This documentation provides a reference to the `upsertSalesChannels` method. This belongs to the Sales Channel Module.
<Note>
You should only use this methods when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
## upsertSalesChannels(data, sharedContext?): Promise&#60;[SalesChannelDTO](../../../interfaces/sales_channel.SalesChannelDTO/page.mdx)&#62;
This method updates or creates a sales channel if it doesn't exist.
@@ -9,6 +9,12 @@ import { TypeList } from "docs-ui"
This section of the documentation provides a reference to the `ISalesChannelModuleService` interface’s methods. This is the interface developers use to use the functionalities provided by the Sales Channel Module.
<Note>
You should only use the methods in this reference when implementing complex customizations. For common cases, check out [available workflows instead](/medusa-workflows-reference).
</Note>
The main service interface for the Sales Channel Module.
## Methods
@@ -8,6 +8,4 @@ import { TypeList } from "docs-ui"
**Event**: `Object`
## Properties
<TypeList types={[{"name":"name","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"data","type":"TData","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"metadata","type":"[EventMetadata](../sales_channel.EventMetadata/page.mdx)","description":"","optional":true,"defaultValue":"","expandable":false,"children":[{"name":"eventGroupId","type":"`string`","description":"","optional":true,"defaultValue":"","expandable":false,"children":[]}]}]} expandUrl="https://docs.medusajs.com/v2/advanced-development/data-models/manage-relationships#retrieve-records-of-relation" sectionTitle="Event"/>
@@ -8,6 +8,4 @@ import { TypeList } from "docs-ui"
**JoinerRelationship**: `Object`
## Properties
<TypeList types={[{"name":"alias","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"foreignKey","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"primaryKey","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"serviceName","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"entity","type":"`string`","description":"","optional":true,"defaultValue":"","expandable":false,"children":[]},{"name":"inverse","type":"`boolean`","description":"In an inverted relationship the foreign key is on the other service and the primary key is on the current service","optional":true,"defaultValue":"","expandable":false,"children":[]},{"name":"isList","type":"`boolean`","description":"Force the relationship to return a list","optional":true,"defaultValue":"","expandable":false,"children":[]},{"name":"args","type":"`Record<string, any>`","description":"Extra arguments to pass to the remoteFetchData callback","optional":true,"defaultValue":"","expandable":false,"children":[]}]} expandUrl="https://docs.medusajs.com/v2/advanced-development/data-models/manage-relationships#retrieve-records-of-relation" sectionTitle="JoinerRelationship"/>
@@ -8,6 +8,4 @@ import { TypeList } from "docs-ui"
**RawMessageFormat**: `Object`
## Properties
<TypeList types={[{"name":"eventName","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"data","type":"TData","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"source","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"object","type":"`string`","description":"","optional":false,"defaultValue":"","expandable":false,"children":[]},{"name":"action","type":"`string`","description":"","optional":true,"defaultValue":"","expandable":false,"children":[]},{"name":"context","type":"Pick&#60;[Context](../../interfaces/sales_channel.Context/page.mdx), \"eventGroupId\"&#62;","description":"","optional":true,"defaultValue":"","expandable":false,"children":[{"name":"eventGroupId","type":"`string`","description":"A string indicating the ID of the group to aggregate the events to be emitted at a later point.","optional":true,"defaultValue":"","expandable":false,"children":[]}]},{"name":"options","type":"`Record<string, any>`","description":"","optional":true,"defaultValue":"","expandable":false,"children":[]}]} expandUrl="https://docs.medusajs.com/v2/advanced-development/data-models/manage-relationships#retrieve-records-of-relation" sectionTitle="RawMessageFormat"/>