Add block strings to GraphQL grammar #282
Open
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.
The GraphQL TextMate grammar did not have separate handling for block strings, which are different from normal string values in that they may contain unescaped characters like quotes. Block strings were matching the
string.quoted.double.graphql
scope, which did not handle these unescaped characters, leading to incorrect results:A new
string.quoted.triple.block.graphql
scope is defined, which matches everything up to the closing"""
:This becomes more important with Apollo Connectors, where the
selection
attribute is often a block string containing mapping selection syntax that may contain special characters.