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.

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

Discussion of changes to default behavior in Jackson 3.0 #870

Open
k163377 opened this issue Dec 15, 2024 · 4 comments
Open

Discussion of changes to default behavior in Jackson 3.0 #870

k163377 opened this issue Dec 15, 2024 · 4 comments
Labels
3.x Issue affecting/planned for Jackson 3.x

Comments

@k163377
Copy link
Contributor

k163377 commented Dec 15, 2024

Create this issue to discuss feature changes to jackson-module-kotlin in preparation for Jackson 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.

Topics

@k163377 k163377 added the 3.x Issue affecting/planned for Jackson 3.x label Dec 15, 2024
@cowtowncoder
Copy link
Member

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
Copy link
Member

Now created:

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

@k163377
Copy link
Contributor Author

k163377 commented Dec 29, 2024

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
Copy link
Member

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. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Issue affecting/planned for Jackson 3.x
Projects
None yet
Development

No branches or pull requests

2 participants