fix: fix weird case transforms like FTLName -> fTLName #901
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
This should now be determinstically mapped to upper/lower camel for types and functions/values respectively. Note that this casing differs from native Go casing in that initialisms/acronyms are never all-caps. That is, FTL casing is: Ftl not FTL.
alecthomas
requested review from
dhanji,
wesbillman and
worstell
as code owners
Closed
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.
This should now be determinstically mapped to upper/lower camel for types and functions/values respectively.
Note that this casing differs from native Go casing in that initialisms/acronyms are never all-caps. That is, FTL casing is: Ftl not FTL.