Discussion of changes to default behavior in `Jackson 3.0`

[k163377]

Create this issue to discuss feature changes to jackson-module-kotlin in preparation for Jackson 3.0.

• Path to Jackson 3.0.0 jackson-future-ideas#72
• https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.0

The release of Jackson 3.0 is a good opportunity to change the default behavior of jackson-module-kotlin.
So, if you have any suggestions, please reply to this issue.

For individual issues, I will create a new issue labeled 3.x and then summarize them in this issue.

Personally, I would like to organize KotlinFeature in particular.

See below for the entire Jackson issue, including the kotlin-module.
https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-2

[cowtowncoder]

Sounds good! I will link this from jackson-future-ideas.

One quick question: should this be converted to a Discussion instead of Issues?

One thing I have done with jackson-databind is having two labels: 3.0 for changes planned for immediate changes (which need to go in major version bump and couldn't go in further 3.x releases; or that I just hope to get out quickly), and 3.x for other things to tackle in 3.x releases (could be 3.0 but likely later).

[cowtowncoder]

Now created:

• Discussion for change: Change default of `DeserializationFeature. FAIL_ON_NULL_FOR_PRIMITIVES` to `true` for 3.0 jackson-future-ideas#79
• jackson-databind issue for possible change: Change default of DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES to true for 3.0 jackson-databind#4858

which determine whether change will be made, and cover actual change if so decided.

[k163377]

One quick question: should this be converted to a Discussion instead of Issues?

I do not use Discussion much and feel that I would like to discuss on the Issue.

Also, my personal feeling is that not many people check Discussion.
If we were to convert, I would like to keep at least this Issue and move only individual agenda items to Discussion.

One thing I have done with jackson-databind is having two labels: ...

Thank you.
At this point I haven't fully sorted out what to do with kotlin-module, but I have at least recognized that it should be prioritized.
Let me check on a few more issues that need to be changed (and I also need to make an announcement to the community).

[cowtowncoder]

I do not use Discussion much and feel that I would like to discuss on the Issue.

Ok, that is up to you wrt Kotlin module. :)

[k163377]

Added #886.