-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Change default of MapperFeature.DEFAULT_VIEW_INCLUSION
to false
in 3.0
#1484
Comments
Thank you for suggesting this: I hope to focus bit more on 3.x planning after getting 2.9 finalized. |
MapperFeature.DEFAULT_VIEW_INCLUSION
default setting
MapperFeature.DEFAULT_VIEW_INCLUSION
default settingMapperFeature.DEFAULT_VIEW_INCLUSION
to false
in 3.0
Being discussed here: based on which change will either made, or not. |
Discussion closed: will proceed with this change. |
@cowtowncoder let's add below to JSTEP-2. Leaving this here because, Currently laptop is blocked to edit anything from github.com. Will comeback and pick this up in 2 days 🥲. * `DEFAULT_VIEW_INCLUSION`: default to `false` (because the most common use case is to only keep properties or fields annotated with `@JsonView`.)
* [databind#1484](https://github.com/FasterXML/jackson-databind/issues/1484) |
@JooHyukKim Will add once it gets completed -- having some problems with PR (#4885). Basically PR initially had 12 fails; could fix/work-around 7 by configuring |
Right, I pulled and checked. Below tests are failing.
|
MapperFeature.DEFAULT_VIEW_INCLUSION
to false
in 3.0MapperFeature.DEFAULT_VIEW_INCLUSION
to false
in 3.0
Down to just 2 failures:
|
In Jackson 2.x,
MapperFeature.DEFAULT_VIEW_INCLUSION
is set totrue
by default, but almost all users set it tofalse
because the most common use case is to only keep properties or fields annotated with@JsonView
.In Spring Framework and Spring Boot, we already modify this default value, but maybe the default setting could be modify in Jackson 3.x in order to avoid confusing users?
The text was updated successfully, but these errors were encountered: