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
If an API endpoint returns a different media type depending on the HTTP status code response, the generated swagger.json emits multiple "produces" elements and the ui only has one "Response content type" drop down list.
I expected the generated swagger.json to indicate the response media type for each HTTP status code response separately.
I expected the ui to have a drop down list for each HTTP status code response.
In this case, I expected the HTTP status code 200 response to only have "plain/text" and the HTTP status code 403 response to only have "problem/application+json".
I believe this requires generating the OpenApi specification schema to OpenApi 3.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi.
Thank you for Swagger-Net.
If an API endpoint returns a different media type depending on the HTTP status code response, the generated swagger.json emits multiple "produces" elements and the ui only has one "Response content type" drop down list.
I expected the generated swagger.json to indicate the response media type for each HTTP status code response separately.
I expected the ui to have a drop down list for each HTTP status code response.
SwaggerNetExamples.zip
In this case, I expected the HTTP status code 200 response to only have "plain/text" and the HTTP status code 403 response to only have "problem/application+json".
I believe this requires generating the OpenApi specification schema to OpenApi 3.
Thank you.
The text was updated successfully, but these errors were encountered: