-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(medusa, link-modules): sales channel <> product module link #5450
feat(medusa, link-modules): sales channel <> product module link #5450
Conversation
🦋 Changeset detectedLatest commit: 7a83b51 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Ignored Deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Have you checked if any other constraints was link to the sales channel etc? |
Perhaps Publishable API keys? |
There are the following relations (if that is what you meant):
I was planning on covering each domain in a separate PR for easier reviewing. |
@fPolic, can I get you to add a changeset before we merge? |
/snapshot-this |
packages/medusa/src/migrations/1698056997411-product-sales-channels-link.ts
Outdated
Show resolved
Hide resolved
🚀 A snapshot release has been made for this PRTest the snapshots by updating your yarn add @medusajs/admin@7.1.5-snapshot-20231024062306 yarn add @medusajs/admin-ui@2.1.5-snapshot-20231024062306 yarn add create-medusa-app@1.2.3-snapshot-20231024062306 yarn add @medusajs/inventory@1.11.1-snapshot-20231024062306 yarn add @medusajs/link-modules@0.2.1-snapshot-20231024062306 yarn add @medusajs/medusa@1.17.2-snapshot-20231024062306 yarn add medusa-file-s3@1.4.0-snapshot-20231024062306 yarn add @medusajs/medusa-js@6.1.2-snapshot-20231024062306 yarn add medusa-plugin-brightpearl@1.3.12-snapshot-20231024062306 yarn add @medusajs/modules-sdk@1.12.1-snapshot-20231024062306 yarn add @medusajs/medusa-oas-cli@0.2.22-snapshot-20231024062306 yarn add @medusajs/orchestration@0.4.2-snapshot-20231024062306 yarn add @medusajs/pricing@0.1.1-snapshot-20231024062306 yarn add @medusajs/product@0.3.1-snapshot-20231024062306 yarn add @medusajs/types@1.11.4-snapshot-20231024062306 yarn add @medusajs/utils@1.10.4-snapshot-20231024062306 yarn add @medusajs/workflows@0.2.4-snapshot-20231024062306
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, we will need to take care to include that into the core right? if the ff is enabled, then when we list the product they must take into account the sales channel. same if the product is isolated? cc @olivermrbl should we create tickets in linear to not forget what needs to be done after
…r-config' into feat/sales-channel-module--joiner-config
# Conflicts: # packages/core-flows/src/handlers/product/attach-sales-channel-to-products.ts # packages/core-flows/src/handlers/product/detach-sales-channel-from-products.ts
…r-config' into feat/sales-channel-module--joiner-config
LGTM, let's merge when 1.19 is out. Will release mid-week |
@fPolic, can I get you to resolve conflicts, so we can merge? |
# Conflicts: # packages/medusa/src/api/routes/admin/products/get-product.ts # packages/medusa/src/api/routes/admin/products/list-products.ts
What