Add @JsonWrapped (to complement @JsonUnwrapped) about jackson-annotations HOT 16 OPEN

Unlocking to allow use of reactions (use "thumbs up" to "vote"). Please no "+1" comments (content-containing comments welcome of course).

from jackson-annotations.

You are right in that annotation itself would be added here, but none of code handling it will be, which is why I think databind is actually better place for this.
But that's fine; we can even just have 2 issues, one for annotation, one for handling, mostly just to have entries for release notes for both.

As to multiple levels, I thought about that, and if that was to be supposed, I don't think we can assume '.' can be used as separator, since it is a legal property name character.
But changing this to allow sequence of ids is easy, like:

@JsonWrapped({ "contact_details", "address" })

and Java annotations also allow omitting arrays to just do single as well

@JsonWrapped("single")

from jackson-annotations.

+1. I'd love if this were added to @JsonProperty with the optional array syntax @cowtowncoder suggested:

@JsonProperty({"address", "housenumber"})

from jackson-annotations.

👍

from jackson-annotations.

👍

from jackson-annotations.

+1

from jackson-annotations.

This would save a lot of boilerplate. +1

from jackson-annotations.

👍

from jackson-annotations.

I would also like to see this feature.
Is there a workaround for this? Especially in combination with mixins?

from jackson-annotations.

Currently custom serialializer/deserializer would be the way to go. Or possibly converting serializer/deserializer using disposable wrapper classes.

from jackson-annotations.

+1 for

@JsonWrapped({ "contact_details", "address" })

from jackson-annotations.

+1

from jackson-annotations.

+1

from jackson-annotations.

+1

from jackson-annotations.

+1

from jackson-annotations.

Enough voting -- locking issue for now, hoping github will add something better than needing to add more +1 comments. :)

from jackson-annotations.