Support annotating additionalProperties field. #170
Merged
Conversation
This file contains 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
joelittlejohn
added a commit
that referenced
this pull request
Apr 14, 2014
…tion Support annotating additionalProperties field.
|
Very nice addition. Thanks Christian! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Added support for annotating the additionalProperties field. Also added @JsonIgnore to this field by default to Jackson 1 and Jackson 2 annotators.
This change is required in scenarios where Jackson's field visibility has been turned up, causing the additionalProperties field to be serialized into the output. Specifically, I was running into this problem when using POJOs from this project with Jongo.