Break out non-JSON request/response content types as tables (#1756)
* Break out non-JSON request/response content types as tables Currently we display this as a table like "image/png|image/jpeg" and description on a single line, but we're using a table. This breaks the join out to individual rows. * changelog
This commit is contained in:
parent
6700f5ddd1
commit
eb22fac5dc
4 changed files with 18 additions and 14 deletions
|
@ -0,0 +1 @@
|
|||
Clearly indicate that each `Content-Type` may have distinct behaviour on non-JSON requests/responses.
|
Loading…
Add table
Add a link
Reference in a new issue