-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Change default of DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES
to true
for 3.0
#4858
Labels
3.0
Issue planned for initial 3.0 release
Comments
cowtowncoder
added
to-evaluate
Issue that has been received but not yet evaluated
3.0
Issue planned for initial 3.0 release
and removed
to-evaluate
Issue that has been received but not yet evaluated
labels
Dec 18, 2024
I assume title should say "change to Sounds like a good change to me. |
cowtowncoder
changed the title
Change default of
Change default of Dec 31, 2024
DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES
to false
for 3.0DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES
to true
for 3.0
@yawkat Thanks, yes fixed that typo. And looks like proposal is passing (5 to 1 voting as of now). |
As per FasterXML/jackson-future-ideas#79, proposal approved, will work on this. |
cowtowncoder
pushed a commit
that referenced
this issue
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your Issue
As of Jackson 2.x,
DeserializationFeature. FAIL_ON_NULL_FOR_PRIMITIVES
defaults to false, allowing coercion from JSONnull
into Javaint
,long
and so on.For some users -- and especially on "low null" languages like Kotlin -- such coercion is rarely expected, so suggestion was made to change the default.
No decision is yet made: discussion for helping decision is here:
FasterXML/jackson-future-ideas#79
this issue is placeholder until decision is made.
The text was updated successfully, but these errors were encountered: