Refactor FieldNamingPolicy.upperCaseFirstLetter #1515
Merged
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.
-Refactor upperCaseFirstLetter in FieldNamingPolicy.
-Add some comments for special case handling
-Add additional test field to keep 100% coverage (branch in loop for checking to not go out of bounds).
-Shorter, faster. Except for the newly added case. I hope no one writes fields without letters.
Benchmark code: https://pastebin.com/63VJWF03
Benchmark run: https://pastebin.com/su29iePu