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
OpenAPI 3 has components field, where one can put request bodies, params, headers, responses and so on and reuse them across operations.
Would it make sense to try to extract common requests, params etc in servant-swagger? For example, if RequestBody combinator is applied to sub-api with multiple Verb's, we could store the spec for it in components.
The text was updated successfully, but these errors were encountered:
For example, I'd like to use $refs to #/components/parameters, #/components/schema, and #components/responses:
paths:
/systems:
get:
summary: "Get status and properties of the system."
tags:
- System
parameters:
- $ref: '#/components/parameters/fields'
responses:
'200':
description: The status and properties of the system.
content:
application/json:
schema:
$ref: '#/components/schemas/Sys'
'500':
$ref: '#/components/responses/500'
As far as I can judge, at the moment servant-openapi3 "only" support #/components/schemas, the rest is inlined.
OpenAPI 3 has components field, where one can put request bodies, params, headers, responses and so on and reuse them across operations.
Would it make sense to try to extract common requests, params etc in servant-swagger? For example, if RequestBody combinator is applied to sub-api with multiple Verb's, we could store the spec for it in components.
The text was updated successfully, but these errors were encountered: