Skip to content
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(workflows,medusa,utils): add medusa v2 feature flag #5603

Merged
merged 14 commits into from
Nov 13, 2023

Conversation

riqwan
Copy link
Contributor

@riqwan riqwan commented Nov 10, 2023

No description provided.

Copy link

changeset-bot bot commented Nov 10, 2023

🦋 Changeset detected

Latest commit: b3d3c11

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages
Name Type
@medusajs/workflows Minor
@medusajs/medusa Patch
@medusajs/utils Minor
medusa-source-shopify Patch
@medusajs/medusa-oas-cli Patch
@medusajs/oas-github-ci Patch

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

Copy link

vercel bot commented Nov 10, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Ignored Deployments
Name Status Preview Comments Updated (UTC)
api-reference ⬜️ Ignored (Inspect) Visit Preview Nov 13, 2023 1:55pm
docs-ui ⬜️ Ignored (Inspect) Visit Preview Nov 13, 2023 1:55pm
medusa-docs ⬜️ Ignored (Inspect) Visit Preview Nov 13, 2023 1:55pm

@riqwan riqwan changed the title feat(): add medusa v2 feature flag feat(workflows,medusa,utils): add medusa v2 feature flag Nov 10, 2023
Comment on lines +203 to +206
// TODO: enable this in the Pricing Module PR
// created_at: expect.any(String),
// updated_at: expect.any(String),
// variant_id: expect.stringMatching(/^variant_*/),
Copy link
Contributor Author

@riqwan riqwan Nov 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pKorsholm FYI: something we missed in the prices response. We have to sneak this in our PRs

expect.objectContaining({ id: "channel-2" }),
expect.objectContaining({ id: "channel-3" }),
],
// TODO: Introduce this in the sale channel PR
Copy link
Contributor Author

@riqwan riqwan Nov 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fPolic do you think this can be added to your PR?

I commented it out because the remote query is not currently returning sales channels

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes!

@riqwan riqwan marked this pull request as ready for review November 10, 2023 13:53
@riqwan riqwan requested a review from a team as a code owner November 10, 2023 13:53
Copy link
Contributor

@olivermrbl olivermrbl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just had a single thought

Copy link
Member

@adrien2p adrien2p left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@olivermrbl
Copy link
Contributor

Should we merge this guys? Think a couple of other PRs are depending on it

@riqwan
Copy link
Contributor Author

riqwan commented Nov 13, 2023

lessgo 🚢 🚢 🚢 ! cc. @adrien2p @fPolic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants