-
-
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
Add @JsonWrapped
#512
Comments
+1 |
1 similar comment
+1 |
I think use of
to produce
or such? |
Can it be built up as we go along?
This would make it simpler to refactor code if we don't have to worry about updating the field name in the annotation. |
I'd have to think about that, but my first thought was that it should be fine to use both |
+1 |
I really love +1 |
+1 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
This probably belongs in jackson-annotations and is a duplicate of #42 |
@Dru89 Actually this is the better place just because while annotations package is where annotation is added, databind implements the behavior. So one is needed for databind regardless. Having two different issues also works from release-notes perspective. |
+1 |
1 similar comment
+1 |
+1 for reducing boilerplate |
+1 |
2 similar comments
+1 |
+1 |
Pointless to add more |
Note: added new "most-wanted" label to make it easier to find these Top Requests. |
It would be nice to have the inverse of
@JsonUnwrapped
.This would enable serializing this class:
To this:
The text was updated successfully, but these errors were encountered: