Support using @Json.Ignore on a type

[SentryMan]

Manually setting the ignore on each field gets old after a while

---

Allows putting @Json.Ignore(serialize=true) on the type such that all properties are not included in deserialisation (or the opposite via @Json.Ignore(deserialize=true).

[SentryMan]

I think we should be good for 3.4 after this

[rbygrave]

This does not make sense to me. Putting @Json.Ignore on the type would be the same as not having any @Json ... unless it means something else??

What is the use case? What does this mean?

[SentryMan]

Putting @Json.Ignore on the type would be the same as not having any @JSON

Remember that you can control both serialization and deserialization with ignore

[SentryMan]

What is the use case? What does this mean?

It's basically like Jacksons's @JsonIgnoreProperties(allowGetters=true/false, allowSetters=true/false)

[rbygrave]

Remember that you can control both serialization and deserialization with ignore

This is the part that was left out of the description, the use case for doing this. I've added that into the description.

[rbygrave]

So what is the actual use case? There is a type and it should not support deserialisation at all?

I'm not sure the current solution is great in that when deserialisation is done it will produce an a type with an empty result - and this seems invalid or un-useful. It more seems that if we turn off deserialisation altogether than it shouldn't be used at all? So I'm wondering what is the actual use case, why do we think an "empty result" is valid?

[SentryMan]

With this you can change the default behavior for a specific class, it can be overridden by the property annotation to a field or by adding the ignore annotation to that field and flipping the boolean

[SentryMan]

See the tests, you can still selectively enable the properties you want.

[SentryMan]

Hmm, it's not as ergonomic as I had hoped. I'll get back to this later