Add benjie's edit to clarify schema coordinates may not include {Igno… #2
Conversation
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
|
Suggest you add this to the agenda for 2 weeks for discussion 👍 |
|
This approach was rejected at today's WG in favour of using a separate grammar for schema coordinates. (Please close when you get a chance @magicmark.) |
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.
This is @benjie's draft edit here: graphql#794 (comment)
We're not confident that this is "worth it" in terms of "polluting" section two with the edge case behaviour of schema coordinates (but I believe we need something to avoid a confusing contradiction)
@benjie I didn't add the "{Ignored} tokens are invalid in a schema coordinate" to the commas section - not sure if this is needed since we already clarify this in the definition of {Ignored} tokens