Support for Jackson field-renames-getter heuristic #461
Conversation
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
added 2 commits February 12, 2014 14:51
…king compatibility with Jackson's own behavkour
| Hi, this was merged in #486 |
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.
Jackson supports the following behaviour:
When rendering JSON with Jackson, the
getFoomethod will correctly be interpreted as belonging to the marshalled "renamed" property.Although support for
@JsonPropertyand@JsonIgnorewere added in #321, the model parser was not respecting renames found at the field level after inspecting a corresponding public getter method. This patch is a fix.Apologies if any of the code is horribly naive - totally open to receiving feedback and making this PR better.