This repository has been archived by the owner on Nov 5, 2021. It is now read-only.
add tokenizer for graphql language variables #78
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
|
|
acao
changed the title
|
👍 Thank you! |
|
thank you! dang, that was fast! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
thought i would add a tokenizer that adds a bit more definition. let me know what you think of my useage of the identifiers? we basically have typed, named function parameters.
adding this for our upcoming custom
monaco-graphql, and for other folks using monaco with graphql language.the next PR I'll come up with will be to add a tokenizer that targets just the argument names (the names in the named parameters)
before:
after:
