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.

Sign up for GitHub

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

Jump to bottom

JsonFormat.Feature.ACCEPT_EMPTY_STRING_AS_NULL_OBJECT not working with null coercion with @JsonSetter #2023

Closed
cowtowncoder opened this issue May 4, 2018 · 0 comments
Closed

JsonFormat.Feature.ACCEPT_EMPTY_STRING_AS_NULL_OBJECT not working with null coercion with @JsonSetter #2023

cowtowncoder opened this issue May 4, 2018 · 0 comments
Milestone
2.9.6

Comments

@cowtowncoder
Copy link
Member

Looks like coercion from null (see #1402) does not yet work if null is result of coercion from empty String, when JsonFormat.Feature.ACCEPT_EMPTY_STRING_AS_NULL_OBJECT is enabled.
But it should.

This is particularly important for XML use case where lack of native null (and resulting confusion between empty String / null) can cause impedance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.9.6
Development

No branches or pull requests
1 participant
@cowtowncoder