Lowercase column names before applying TitleCase
#1357
Closed
Conversation
This file contains 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
esdrasbeleza
changed the title
TitleCase
|
This would be a breaking change for many users, so I will close this. For your case, I suggest renaming them using aliases. |
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.
I have a database which I cannot change and all the fields are in
SCREAMING_SNAKE_CASE.When I generate my models,
USER_IDbecomesUSER_IDin my Go structs, which is not what I want and doesn't follow the expected Go conventions: I expect my field to be generated asUserID.This small change will make my model be properly generated.