Skip to content

Make JsonReadContext non-final #1421

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

Closed
isalvadori opened this issue Apr 24, 2025 · 4 comments
Closed

Make JsonReadContext non-final #1421

isalvadori opened this issue Apr 24, 2025 · 4 comments
Labels
2.19 Issues planned at earliest for 2.19
Milestone

Comments

@isalvadori
Copy link

After opening a discussion here about the need (or not) for the JsonReadContext to be final, it turned out there is no strong reason behind having it final.
Thus, I would like to propose to remove the final on that class.
This will allow easier customization of the context.

@maho7791
Copy link

I wanted to mention that we would need this also for the 3.x versions.
We currently move our EMF mapping for jackson3.

@cowtowncoder cowtowncoder added the 2.19 Issues planned at earliest for 2.19 label Apr 24, 2025
@cowtowncoder
Copy link
Member

Yes, we merge forward changes in most cases, and do so here.

@cowtowncoder cowtowncoder changed the title Make JsonReadContext non final Make JsonReadContext non-final Apr 24, 2025
@maho7791
Copy link

This was faster than light!!!

@cowtowncoder
Copy link
Member

@maho7791 fwtw this was due to lucky timing. It's not always this fast -- but sometimes that happens which is great :)

@cowtowncoder cowtowncoder added this to the 2.19.0 milestone Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.19 Issues planned at earliest for 2.19
Projects
None yet
Development

No branches or pull requests

3 participants