Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Field name aliasing broken if naming strategy used #276

Closed
shdunning opened this issue May 29, 2018 · 0 comments
Closed

Field name aliasing broken if naming strategy used #276

shdunning opened this issue May 29, 2018 · 0 comments

Comments

@shdunning
Copy link

One of the cool features of this library is that we can set field naming strategy like so...

extra.SetNamingStrategy(extra.LowerCaseWithUnderscores)

..however, then we can no longer rename fields using json tags; that is, the naming strategy forces the responses to always follow the naming strategy. This can be too restrictive in a production environment where we want a separation between the data and API models.

PR #275 proposes a fix for this issue.

@taowen taowen closed this as completed in ab8a2e0 Jul 1, 2018
zhenzou pushed a commit to zhenzou/jsoniter that referenced this issue Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant