-
Notifications
You must be signed in to change notification settings - Fork 130
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
Add support for contract-based app modules #4465
Conversation
Thanks for your contribution! Depending on what you are working on, you may want to request a review from a Shopify team:
|
Coverage report
Show files with reduced coverage 🔻
Test suite run success1890 tests passing in 858 suites. Report generated by 🧪jest coverage report action from c0478b4 |
We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset. |
...field, | ||
// NOTE: we're not using this id anywhere, generating it to satisfy the schema | ||
// decided not to remove it from the schema for now to minimize the risk of breaking changes | ||
id: randomUUID(), |
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.
is there an alternative way for us to generate this id
in CLI since it's been removed here?
WHY are these changes introduced?
We need to support app modules that define their schema using contracts. We already had this for
data
, but that solution only supported config-extensions (defined in the app.toml).This solution adds support for contract-based non-config modules.
WHAT is this pull request doing?
Add a new
createContractBasedModuleSpecification
to easily generate this kind of specifications.Apply it to marketing activity extension and remove the custom config for it.
How to test your changes?
Post-release steps
Measuring impact
How do we know this change was effective? Please choose one:
Checklist