Ignoring unknown properties on de-serializing process#373
Merged
komamitsu merged 1 commit intomsgpack:developfrom Jul 9, 2016
Merged
Ignoring unknown properties on de-serializing process#373komamitsu merged 1 commit intomsgpack:developfrom
komamitsu merged 1 commit intomsgpack:developfrom
Conversation
Member
|
👍 |
Member
|
@marenzo Thanks! |
Contributor
Author
|
@komamitsu thanks for merging :) could you ping me when you'll release new version? |
Member
|
@marenzo We released 0.8.8 a few weeks ago that includes this feature. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #358
Having two entities, similar in fields except one may contain extra one, ObjectMapper will fail to de-serialize as it expects the payload to have exact same number of fields (properties) on the value type object.
Consider such case:
Previous client could handle a case when de-serializing the payload of Pojo2 into Pojo1.
This is totally solvable by adding
@JsonIgnorePropertiesannotation, but since we already haveJsonArrayFormatas helper for backward-compatibility, thought it also should be part of this utility.