Normalize Field Names #49
Merged
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
aj-foster
force-pushed
the
aj/normalize-field-names
branch
3 times, most recently
from
5653314
to
febab20
Compare
aj-foster
force-pushed
the
aj/normalize-field-names
branch
from
febab20
to
59f3ea4
Compare
aj-foster
force-pushed
the
aj/normalize-field-names
branch
from
d00c101
to
e0719e2
Compare
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.
Field names featuring dashes and other interesting characters have the potential to create interesting generated code. This PR normalizes field names during processing.