BUGFIX: allow json tag overrides with set naming strategy #275
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 allows users to use a set naming strategy, like so...
extra.SetNamingStrategy(extra.LowerCaseWithUnderscores)
...but also alias a field via the json tag to rename it:
The above will result in the following JSON structure:
{"var":"some string value", "foo_bar":"some other string value"}
.Prior to this change, one could not alias a struct field via the
json
tag to rename and have a set naming strategy.