[Bugfix] Escape enum literals starting with underscore#329
Merged
budde377 merged 1 commit intoheftapp:mainfrom Dec 7, 2023
Merged
[Bugfix] Escape enum literals starting with underscore#329budde377 merged 1 commit intoheftapp:mainfrom
budde377 merged 1 commit intoheftapp:mainfrom
Conversation
Contributor
|
Great catch! Thanks for submitting. |
Contributor
Author
|
Great, glad I could help and thanks for your work, very useful project! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've noticed that enum literals remain private when the enum literals are prefixed with an underscore in the graphql schema.
This PR adds functionality which escapes enum literals starting with an underscore just like property names.