Add more case transformations #114
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add strict versions of PascalCase and camelCase, as well as CONST_CASE from #95, with respective basic test cases. Based on my experience, the former two are used extensively at least in C# and JavaScript/TypeScript. In fact, I don't personally know another language that strongly encourages retaining all caps segments in a camel/pascal-case identifier (DBName rather than DbName) other than Go.
Not adding UPPERCASE and lowercase transformations, as the supposed use case referred to by the OP would most probably be achieved by quoting entity names in SQL queries, or using either snake_case (PostgreSQL) or CONST_CASE (SQL standard), so the word boundaries are retained. If anybody does indeed need pure case conversions (could also be that they were using _ in Go identifiers, uhh...), feel free to reply here.