Fix regex patterns for gql parsing to allow for whitespace#920
Open
Namyts wants to merge 1 commit intoAnWeber:mainfrom
Open
Fix regex patterns for gql parsing to allow for whitespace#920Namyts wants to merge 1 commit intoAnWeber:mainfrom
Namyts wants to merge 1 commit intoAnWeber:mainfrom
Conversation
Allow for whitespace between query and opening curly bracket. It previously interpreted the curly as the operation name
This file contains hidden or 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.
Allow for whitespace between query and opening curly bracket. It previously interpreted the curly as the operation name.
because
{"query":"query {\n __schema {\n types {\n name\n }\n }\n}","operationName":"{"}Added to all 3 regexes for consistency, but I am only concerned about query & mutation