-
Notifications
You must be signed in to change notification settings - Fork 42
Issues: graphql-dotnet/parser
Ensure October spec compliance before v8 release and publish ...
#206
opened Jan 22, 2022 by
sungam3r
Open
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
All literals should have proper indentation in case of preceding comments
bug
Something isn't working
#314
opened Apr 21, 2023 by
sungam3r
Ensure October spec compliance before v8 release and publish release
spec compliance
The change is intended to solve the problem of inconsistency with the official GraphQL specification
#206
opened Jan 22, 2022 by
sungam3r
Lexer can still allocate memory in the case of parsing strings with escape characters
performance
#103
opened Jan 10, 2021 by
sungam3r
ProTip!
Follow long discussions with comments:>50.