Restore usage of custom app passwords to theme commands
WHY are these changes introduced?
- Closes https://github.com/Shopify/cli/issues/6415
This was previously stripped away but theme developers are still using this flow and are forced to pin to older versions. I'm returning the functionality in this PR but calling out the specific places where it doesn't work:
devdoes not support hot module reloadingconsoleandprofilecommands do not work at all
I tested on all of the theme commands:
check - β
console - β
delete - β
dev - π‘
duplicate - β
info - β
init - β
language-server - β
list - β
open - β
package - β
profile - β
publish - β
pull - β
push - β
rename - β
share - β
For console and profile we now throw an AbortError. For dev we render a warning.
How to test your changes?
- Install the snapped version
npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/[email protected] - Run through as many of the commands as you'd like to test
Coverage report
St.:grey_question: |
Category | Percentage | Covered / Total |
|---|---|---|---|
| π‘ | Statements | 79.2% (-0.02% π») |
13647/17230 |
| π‘ | Branches | 73.05% (-0.05% π») |
6648/9100 |
| π‘ | Functions | 79.36% (-0.01% π») |
3518/4433 |
| π‘ | Lines | 79.57% (-0.02% π») |
12892/16203 |
Show new covered files π£
St.:grey_question: |
File | Statements | Branches | Functions | Lines |
|---|---|---|---|---|---|
| π’ | ... / bulk-operation-run-mutation.ts |
100% | 100% | 100% | 100% |
| π’ | ... / bulk-operation-run-query.ts |
100% | 100% | 100% | 100% |
| π’ | ... / staged-uploads-create.ts |
100% | 100% | 100% | 100% |
| π’ | ... / execute-bulk-operation.ts |
95.24% | 85.71% | 100% | 95% |
| π’ | ... / run-mutation.ts |
100% | 100% | 100% | 100% |
| π’ | ... / run-query.ts |
100% | 100% | 100% | 100% |
| π‘ | ... / stage-file.ts |
74.29% | 53.33% | 85.71% | 73.53% |
Show files with reduced coverage π»
St.:grey_question: |
File | Statements | Branches | Functions | Lines |
|---|---|---|---|---|---|
| π’ | ... / ConcurrentOutput.tsx |
98.36% (-1.64% π») |
92% (-4% π») |
100% | 98.33% (-1.67% π») |
| π΄ | ... / ui.tsx |
50.82% (-0.79% π») |
42.86% (-5.53% π») |
54.55% (+1.42% πΌ) |
50% (-0.82% π») |
| π’ | ... / console.ts |
81.82% (+15.15% πΌ) |
75% (-25% π») |
100% (+33.33% πΌ) |
81.82% (+15.15% πΌ) |
| π΄ | ... / dev.ts |
12.77% (-0.57% π») |
2.78% (-0.16% π») |
57.14% | 12.77% (-0.57% π») |
| π‘ | ... / theme-environment.ts |
69.57% (-1.86% π») |
50% | 55.56% (-3.27% π») |
69.57% (-1.86% π») |
Test suite run success
3365 tests passing in 1377 suites.
Report generated by π§ͺjest coverage report action from 56c08f7c089b0c7e36537c0575a5096bd31379da
/snapit
π«°β¨ Thanks @graygilmore! Your snapshot has been published to npm.
Test the snapshot by installing your package globally:
npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/[email protected]
[!CAUTION] After installing, validate the version by running just
shopifyin your terminal. If the versions don't match, you might have multiple global instances installed. Usewhich shopifyto find out which one you are running and uninstall it.
We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.
[!CAUTION] DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.
Force Push Patch Notes
- Updated to note that password protected storefronts also don't work
Thanks to both @dejmedus and @EvilGenius13 for the tophatting π