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.

Sign up for GitHub

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

Jump to bottom

Extend internal bitfield of MapperFeature to be long #3033

Closed
cowtowncoder opened this issue Jan 30, 2021 · 1 comment
Closed

Extend internal bitfield of MapperFeature to be long #3033

cowtowncoder opened this issue Jan 30, 2021 · 1 comment
Milestone
2.13.0

Comments

@cowtowncoder
Copy link
Member

Ok so something I figured might never occur -- number of MapperFeature fields filling int -- seems to be happening. Although with 3.0 we can remove/refactor some of them, this will not help 2.x, and we probably still need to add couple more in 2.x timeframe. Because of this, it probably makes sense to upgrade internal bitfield to use long: it should be mostly fine (I think there is just one theoretical gnarly part), and should go in 2.13.
@cowtowncoder cowtowncoder added this to the 2.13.0 milestone Feb 26, 2021
@cowtowncoder
Copy link
Member Author

Implemented: the main/only potential concern is with frameworks -- if there is any way that configurator in, say, Spring, might be using MapperFeature.getMask() or enabledIn(int)...
I hope 2.13.0 release candidates can help there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.13.0
Development

No branches or pull requests
1 participant
@cowtowncoder