-
Notifications
You must be signed in to change notification settings - Fork 15
Convert @ApiModel(reference) to @Schema(ref) or @Schema(implementation)
#60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@ApiModel(reference) to @Schema(ref) or @Schema(implementation)
|
@simoneromani-90 hope you agree with the changes here! Thanks again for calling these out. |
Laurens-W
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| return; | ||
| } | ||
| String referenceValue = literal.getValue().toString(); | ||
| if (referenceValue.contains("://")) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder, could this be a local file reference? In that case this doesn't work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It actually can, so we should expand this to also check for #
These are examples of local references (within and outside of the current spec)
"common-models.json#/definitions/Address"
"#/definitions/MyModel"
@ApiModel(reference)migration should support both@Schema(ref)and@Schema(implementation)based on value being an URL or class name #54