Enable remove rest future flag #898
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
byrichardpowell
force-pushed
the
enable-remove-rest-future-flag
branch
from
eac09de to
3e3a450
Compare
lizkenyon
approved these changes
Dec 5, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Dec 5, 2024
Enable remove rest future flag
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHY are these changes introduced?
Shopify is all-in on graphql. We added this future flag to the shopify-app-remix package so developers can progressively remove REST. Now we want to make sure that new apps don't use REST only to have to migrate to GraphQL
WHAT is this pull request doing?
Test this PR
Checklist
README.mdfile and other related documentation, if applicableCHANGELOG.md