You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The question hasn't been asked or answered. The issue: Swagger 3.0.0 doesn't allow to overwrite the global response model that we defined in "createDocket()" method by using @ApiResponse(response = SomeErrorModel.class). We have a different responses types for the same error (500) and can't go with a common response model for this error.
What version of the library are you using? Is it the latest version? The latest released version is
Question. Is this a question about how to do a certain thing? Yes, please describe how to set response model for specific error in @ApiResponse annotation ("response" parameter doesn't work anymore)?
Feature Request. Could you please re-add the option to define the response model (not example value) in @ApiResponse annotation like it worked in Swagger 2.x.x? We'd not like to stay with the deprecated classes (ModelRef, ResponseMessage, ResponseMessageBuilder) to have this functionality.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The question hasn't been asked or answered. The issue: Swagger 3.0.0 doesn't allow to overwrite the global response model that we defined in "createDocket()" method by using @ApiResponse(response = SomeErrorModel.class). We have a different responses types for the same error (500) and can't go with a common response model for this error.
Our dependencies: springfox-swagger2 3.0.0, springfox-swagger-ui 3.0.0, spring-plugin-core 2.0.0.RELEASE.
What kind of issue is this?
Question. Is this a question about how to do a certain thing? Yes, please describe how to set response model for specific error in @ApiResponse annotation ("response" parameter doesn't work anymore)?
Feature Request. Could you please re-add the option to define the response model (not example value) in @ApiResponse annotation like it worked in Swagger 2.x.x? We'd not like to stay with the deprecated classes (ModelRef, ResponseMessage, ResponseMessageBuilder) to have this functionality.
Expected usage:
Thanks!
Best regards,
Olya
The text was updated successfully, but these errors were encountered: