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

Deprecate DefaultTyping.EVERYTHING in 2.x and remove in 3.0 #4160

Closed
JooHyukKim opened this issue Oct 15, 2023 · 3 comments · Fixed by #4240
Closed

Deprecate DefaultTyping.EVERYTHING in 2.x and remove in 3.0 #4160

JooHyukKim opened this issue Oct 15, 2023 · 3 comments · Fixed by #4240
Labels
2.17 Issues planned at earliest for 2.17 3.x

Comments

@JooHyukKim
Copy link
Member

Is your feature request related to a problem? Please describe.

As per JavaDoc of ObjectMapper.DefaultTyping.EVERYTHING itself, users are better off without it, even though was initally created off a feature request. So I propose that we remove it progressively.

Describe the solution you'd like

  1. Deprecate in 2.x, then
  2. remove in 3.0

Usage example

No response

Additional context

No response

@JooHyukKim JooHyukKim added the to-evaluate Issue that has been received but not yet evaluated label Oct 15, 2023
@JooHyukKim JooHyukKim changed the title Deprecate ObjectMapper.DefaultTyping.EVERYTHING in 2.x and remove in 3.0 Deprecate DefaultTyping.EVERYTHING in 2.x and remove in 3.0 Oct 15, 2023
@cowtowncoder cowtowncoder added 3.x and removed to-evaluate Issue that has been received but not yet evaluated labels Oct 16, 2023
@cowtowncoder cowtowncoder added the 2.17 Issues planned at earliest for 2.17 label Oct 24, 2023
@timnick-snow
Copy link

When is 3.0 planned to be released ?

@JooHyukKim
Copy link
Member Author

When is 3.0 planned to be released ?

Please ask over at https://github.com/FasterXML/jackson/discussions, unless the question is related to the issue in which case we need more detail. 👍🏼

@cowtowncoder
Copy link
Member

@timnick-snow It being a major new version, sometime after 2.17 gets ready I would hope. It has been going on along side for years now, unfortunately. No firm date/plan -- my hope is to rewrite property introspection logic in 2.x and then move on to focus on 3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.17 Issues planned at earliest for 2.17 3.x
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants