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
When having a different content type than application/json or application/xml the rendering of the schema is slightly confusing. E.g. we use application/jose at some points of our spec and it doesn't get rendered at all (see image below)
When using something like that I would expect it to render at least : string as it does it with text/plain since application/jose is represented as a base64 string.
Below you can find an attached example.
Example spec
openapi: 3.0.0info:
version: 4.2.0title: Whatsoeverdescription: nahpaths:
/ep:
post:
summary: POST stuffrequestBody:
required: truecontent:
application/jose:
schema:
title: Titledescription: This is a descriptiontype: stringexamples:
E1:
value: ajasdjasdsadtext/plain:
schema:
title: Titledescription: This is a descriptiontype: stringexamples:
E1:
value: ajasdjasdsadresponses:
'200':
description: OKcontent:
application/jose:
schema:
title: Anlagedescription: Verschlüsselte Anlage im Format JSON Web Encryption (JWE) laut RFC7516type: stringpattern: '^[a-zA-Z0-9-_=.]+$'
The text was updated successfully, but these errors were encountered:
When having a different content type than
application/json
orapplication/xml
the rendering of the schema is slightly confusing. E.g. we use application/jose at some points of our spec and it doesn't get rendered at all (see image below)When using something like that I would expect it to render at least
: string
as it does it withtext/plain
sinceapplication/jose
is represented as a base64 string.Below you can find an attached example.
Example spec
The text was updated successfully, but these errors were encountered: