Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support `@JsonUnwrapped` with `@JsonCreator` (if possible)
See original GitHub issue(note: follow-up for #265)
Current implementation of @JsonUnwrapped deserialization requires handling of all other properties first, and only then reconstructing unwrapped objects. This works ok via fields/setters, but can not work with @JsonCreator passed values.
But with a major rewrite it should be possible to make this work. This probably requires more support for actually determining unwrapped-properties a priori, instead of just buffering anything that doesn’t match. Or maybe it only requires more logic in handling of creator.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:30
- Comments:17 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Implementation of this is necessary to use
@JsonUnwrappedin Kotlin.@OverlyExcessive It works just fine with deserialization if you use setters (or fields). Note that you do NOT have to pass ALL properties via creator; mixing and matching creator and setters/fields is legal.
This is not to say it wouldn’t be great to allow passing unwrapped properties via Creator methods, just that this is the one aspect with unwrapped properties that does not work.