-
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
Gate GraphiQL for Shopifolk only #2821
Conversation
Thanks for your contribution! Depending on what you are working on, you may want to request a review from a Shopify team:
|
We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset. |
Coverage report
Show files with reduced coverage 🔻
Test suite run success1432 tests passing in 671 suites. Report generated by 🧪jest coverage report action from b0b6977 |
I added fixes for 2 issues:
For now, in both cases, we simply shouldn't show the option to open GraphiQL. |
00b181d
to
30c0b60
Compare
This is necessary because we have to add an OAuth callback URL. If we are not updating URLs, GraphiQL won't work.
30c0b60
to
b0b6977
Compare
Nice! Once this is in nightly I can recommend its usage with the flag 😃 |
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.
Working as expected 👌
WHY are these changes introduced?
If a sudden need arises to ship
main
as a new release, we shouldn't block it just because GraphiQL is still ripening.WHAT is this pull request doing?
For Shopifolk/spin, things proceed as before. For external parties, GraphiQL is an opt-in via env var
SHOPIFY_CLI_ENABLE_GRAPHIQL_EXPLORER
.How to test your changes?
Measuring impact
How do we know this change was effective? Please choose one:
Checklist
dev
ordeploy
have been reflected in the internal flowchart.