-
-
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
Comments
I assume title should say "change to Sounds like a good change to me. |
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. |
Per-test modification needed after #4884 merged.
|
@cowtowncoder Made fixes to most of modules. all failing tests seem to be reasonable (nothing buggy). May I ask for help with Scala module @pjfanning ? |
@JooHyukKim yes, @pjfanning maintains Scala module and should be able to help. Looks like it's only 4 test failures, fortunately:
|
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: