internal/dinosql: Fix incorrect enum names #223
Merged
Conversation
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
Enums of type enum_type with values like foo-bar should be named EnumTypeFooBar, but were being generated as EnumTypeFoobar. The regex pattern I was using to remove unsupported characters was accidentally stripping out underscores, the character used to split the string.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enums of type enum_type with values like foo-bar should be named
EnumTypeFooBar, but were being generated as EnumTypeFoobar.
The regex pattern I was using to remove unsupported characters was
accidentally stripping out underscores, the character used to split the
string.
Fixes #222