-
Notifications
You must be signed in to change notification settings - Fork 762
confirm response for operation is clear #325
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
Comments
Here is the code that takes responses and handles them: https://github.com/swagger-api/swagger-js/blob/develop_2.0/lib/types/operation.js#L117 It will only create a |
@whitlockjc this logic looks good to me. Do we need to change any code? |
Code would change since we'd need to create a |
This is not a regression. The feature/bug that led to this was that swagger-ui wants to render rich representations for the non-default response. To be able to do this, we would need to make This is a new feature, not a regression. |
@whitlockjc my bad for taking a while to get back to this. I believe we actually used to return rendering operations for all models inside response codes. |
I looked into this and the release prior to my involvement didn't have this. I'll have to look back further to see how it was done and we'll get it knocked out. |
This has been implemented |
Need to make sure the response code/schema is clear for non-200 responses.
The text was updated successfully, but these errors were encountered: