Add support for @JsonView
#1209
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
Closes smallrye#1008 Signed-off-by: Michael Edgar <michael@xlate.io>
MikeEdgar
force-pushed
the
issue-1008-jsonview
branch
from
5a3f956 to
83a6447
Compare
phillip-kruger
approved these changes
Aug 8, 2022
|
Thanks @MikeEdgar ! |
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.
Closes #1008
When endpoints responses and request bodies are found with
@JsonView, the schema tree generated from the scan will include the name(s) of the views that were applied to the request/response. For cases where a nested bean should not be different between the views, the user may annotate a field with@Schema(ref = "<NameOfCommonSchema>").Users will likely want to set
mp.openapi.extensions.smallrye.remove-unused-schemas.enabletotrue.