Add support for renaming fields - #98
Merged
Merged
Conversation
Adds a `rename` option to a struct definition. This takes either a string describing a rename method (``"lower"``, ``"upper"``, ``"camel"``, or ``"pascal"`` for lowercase, UPPERCASE, camelCase, or PascalCase respectively), or a callable from str -> str that will be called on every field name. Renamed fields are used for encoding/decoding only, and are intended for cases where you need the JSON field names to be something different than what you wish to use in Python (a common case would be applying camelCase to encoded JSON, but using snake_case in python).
Closed
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
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.
Adds a
renameoption to a struct definition. This takes either a string describing a rename method ("lower","upper","camel", or"pascal"for lowercase, UPPERCASE, camelCase, or PascalCase respectively), or a callable from str -> str that will be called on every field name. Renamed fields are used for encoding/decoding only, and are intended for cases where you need the JSON field names to be something different than what you wish to use in Python (a common case would be applying camelCase to encoded JSON, but using snake_case in python).Example:
Todo: