Add support for @ApiObjectField annotations on getters and setters #165
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
added 3 commits
October 26, 2015 14:23
object marked with @ApiObject If you mark an object with @ApiObject, fields not marked with @ApiObjectField are silently ignored so you are forced to add @ApiObjectField to all fields.
…ters fabiomaffioletti#163 To be able to support Google AutoValue (https://github.com/google/auto/tree/master/value) it would be nice if the @ApiObjectField annotation cound be placed on getters and setters of the abstract object, as the fields themselves are not available to the restcontroller.
…rs and setters Improved unit tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
To keep backwards compatibility, methods must be annotated with @ApiObjectField to be interpreted as field definitions.
References issues #163 and #164.