Skip to content

Issues: graphql-dotnet/parser

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

7 Open 52 Closed
7 Open 52 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Handle whitespaces somehow
#360 opened Oct 16, 2023 by sungam3r
3
Fix broken indentation bug Something isn't working
#348 opened Oct 11, 2023 by sungam3r
All literals should have proper indentation in case of preceding comments bug Something isn't working
#314 opened Apr 21, 2023 by sungam3r
Add tests to increase code coverage up to 100%
#309 opened Apr 20, 2023 by sungam3r
Optimize comments and block strings performance
#217 opened Jan 26, 2022 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.