-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Json binding should use the field local name #389
Comments
tefra
added a commit
that referenced
this issue
Jan 20, 2021
tefra
added a commit
that referenced
this issue
Jan 20, 2021
tefra
added a commit
to tefra/xsdata-w3c-tests
that referenced
this issue
Jan 20, 2021
tefra
added a commit
to tefra/xsdata-samples
that referenced
this issue
Jan 20, 2021
tefra
added a commit
to tefra/xsdata-samples
that referenced
this issue
Jan 20, 2021
tefra
added a commit
to tefra/xsdata-w3c-tests
that referenced
this issue
Jan 20, 2021
Hello, is it possible to make this optional? I went to upgrade this dependency in a project that relies on the json output having different key names and afaict it's not possible to make it output Specifically here, https://github.com/tefra/xsdata/blob/v22.11/xsdata/formats/dataclass/serializers/json.py#L104 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The parser/serializer always the field definition names instead of the metadata names like their xml counterparts.
The text was updated successfully, but these errors were encountered: