-
Notifications
You must be signed in to change notification settings - Fork 315
Closed
Description
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.0
info:
version: 4.2.0
title: Whatsoever
description: nah
paths:
/ep:
post:
summary: POST stuff
requestBody:
required: true
content:
application/jose:
schema:
title: Title
description: This is a description
type: string
examples:
E1:
value: ajasdjasdsad
text/plain:
schema:
title: Title
description: This is a description
type: string
examples:
E1:
value: ajasdjasdsad
responses:
'200':
description: OK
content:
application/jose:
schema:
title: Anlage
description: Verschlüsselte Anlage im Format JSON Web Encryption (JWE) laut RFC7516
type: string
pattern: '^[a-zA-Z0-9-_=.]+$'Metadata
Metadata
Assignees
Labels
No labels
