fix: Escape special chars in enum name#283
Merged
fabien0102 merged 1 commit intofabien0102:mainfrom Feb 4, 2025
Merged
Conversation
Merged
This was referenced Feb 13, 2026
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.
Similar to #207 however addressing the issue more generally.
Enum names could contain characters that are not allowed to be used as identifiers. The best example is a string starting with a number, however it could also be like in the example "danish–swedish farmdog" a string using
–which is\u2013.As several issues are already solved by using
pascal(-) it acts as a last resort if even this fails.