-
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
Remove unified deployments beta flag code #2936
Conversation
Thanks for your contribution! Depending on what you are working on, you may want to request a review from a Shopify team:
|
98d6641
to
7f43432
Compare
2c94a65
to
a35a74e
Compare
a35a74e
to
28d0300
Compare
28d0300
to
87862af
Compare
Coverage report
Show files with reduced coverage 🔻
Test suite run success1430 tests passing in 664 suites. Report generated by 🧪jest coverage report action from b49cce5 |
We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset. |
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.
Nice work! 🔥
I've checked that everything keeps working and commented a few things that I don't understand, but they are probably fine.
packages/app/src/cli/services/dev/processes/draftable-extension.ts
Outdated
Show resolved
Hide resolved
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.
Looks and works great!! I just have some questions about removing what seemed to be legacy functions code from before they moved onto the app module framework.
Also, do you want to keep set_beta_flag.ts
around, or can it be removed too?
} | ||
|
||
const functionExtensions = options.app.allExtensions.filter((ext) => ext.isFunctionExtension) | ||
functionExtensions.forEach((ext) => (ext.usingExtensionsFramework = true)) |
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.
Can this logic be removed now that all functions are on the app module framework?
All good points, thanks @mattnoakes , I'll address them! |
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.
Thanks for addressing our feedback!! Everything still works!
I should have addressed all feedback but for some reason the test coverage run fails 🤔 |
This reverts commit 59c81b6.
I've removed the code that deals with legacy functions, I'd rather have that in a separate PR. @mattnoakes could I get another round of QA just to be extra sure? Everything should still work. If it does we can merge tomorrow. |
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.
Looks good! Deploy works as expected!
title: 'C', | ||
type: 'PRODUCT_DISCOUNTS', | ||
} | ||
|
||
const LOCAL_APP = (uiExtensions: ExtensionInstance[], functionExtensions: ExtensionInstance[] = []): AppInterface => { |
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.
const LOCAL_APP = (uiExtensions: ExtensionInstance[], functionExtensions: ExtensionInstance[] = []): AppInterface => { | |
const LOCAL_APP = (uiExtensions: ExtensionInstance[]): AppInterface => { |
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.
I'm going to keep the function related changes separate from this PR, we can go around and clean them up later.
d656f30
to
b49cce5
Compare
Differences in type declarationsWe detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:
New type declarationsWe found no new type declarations in this PR Existing type declarationspackages/cli-kit/dist/public/node/ruby.d.ts@@ -12,7 +12,6 @@ interface ExecCLI2Options {
signal?: AbortSignal;
stdout?: Writable;
stderr?: Writable;
- unifiedDeployment?: boolean;
}
/**
* Execute CLI 2.0 commands.
|
WHY are these changes introduced?
We still have code that deals with simplified deployments branching logic. Because everyone is on simplified deployments now we can remove that code.
WHAT is this pull request doing?
I've removed what I could find related to unified deployments. We still need to differentiate between releasing or not releasing when doing a deploy so I've changed the
mode
to a simplerelease
boolean.Also, we don't need to fetch functions anymore as part of the
fetchAppExtensionRegistrations
query.How to test your changes?
Run
deploy
anddeploy --no-release
and everything should work.