Jackson 3.0.0 default for MapperFeature.DEFAULT_VIEW_INCLUSION

[cowtowncoder]

(part of #72 uber-Discussion)

As of Jackson 2.x, MapperFeature.DEFAULT_VIEW_INCLUSION defaults to true for backwards-compatibility. This means that by default, properties not annotated with any @JsonView are INCLUDED.

A suggestion has been made:

FasterXML/jackson-databind#1484

to change it to false instead, so only explicitly annotated properties are included.
We cannot make the change in Jackson 2.x, but could change it for 3.0.0.

So let's see if there is consensus on whether to make proposed change.

Note on Framework defaults

• Spring: defaults to false (i.e. different from Jackson 2.x defaults)

[sdeleuze]

I voted to change it to false, that makes sense for most use cases IMO and would align with Spring defaults.

[JooHyukKim]

Thanks!

[cowtowncoder]

Thank you for the explanation @sdeleuze. In fact, I have been wondering about how to collaborate with frameworks more close, since I think defaults of Spring and others are form of "voting" too -- maintainers have determined which defaults they think make most sense, likely based on feedback by their own users too.
So +1 for both voting and explaining rationale.

[JooHyukKim]

Got me thinking it may be worth asking other frameworks/library teams about their customized-default configurations and their future plans for change as well. Then count those as votes after informing them.

[cowtowncoder]

That'd be possible but for now but maybe it'd be good to just add separate list of bulletin points for framework defaults in description, where known. Will do that wrt Spring here.