Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid parse ambiguity on types & extensions #127

Closed
sungam3r opened this issue Apr 9, 2021 · 0 comments · Fixed by #169
Closed

Avoid parse ambiguity on types & extensions #127

sungam3r opened this issue Apr 9, 2021 · 0 comments · Fixed by #169
Labels
spec compliance The change is intended to solve the problem of inconsistency with the official GraphQL specification
Milestone
8.0

Comments

@sungam3r
Copy link
Member

sungam3r commented Apr 9, 2021

See graphql/graphql-spec#598

Make sure the parser handles it.
@sungam3r sungam3r added the spec compliance The change is intended to solve the problem of inconsistency with the official GraphQL specification label Apr 9, 2021
@sungam3r sungam3r added this to the 8.0 milestone Nov 9, 2021
@sungam3r sungam3r mentioned this issue Jan 8, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec compliance The change is intended to solve the problem of inconsistency with the official GraphQL specification
Projects
None yet
Milestone
8.0
Development

Successfully merging a pull request may close this issue.

Add ambiguity test graphql-dotnet/parser
1 participant
@sungam3r