fix(Query validate: false) support skipping validation to live on the wild side #790
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
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.
You can save a few ms if you know for sure that your query is valid (eg, static queries which were validated in development/test, as with github/graphql-client)
If you run an invalid, lots of safeguards are thrown out the window:
only:/except:may be visibleThe validation step involves a full visit to the AST, we can't skip that because we have to do a rewrite to InternalRepresentation. Soon, I will refactor that step to be static, so you can run it at build-time and never parse/visit the AST again :)