OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
It is possible to require a specific field in multipart form data in v2 but I don't see any notion of this in v3 spec and Swagger docs. v2: https://swagger.io/docs/specification/2-0/file-upload/,...
In OpenAPI 3.0 server objects can be defined at three basic levels: 1) entire JSON document (global - all resources and operations), 2) a path (all operations on a resource),...
I understand how to represent in 2.0 and 3.0 these query parameters with OpenAPI: ``` ?list=x&list=y ``` But I can't understand if it is possible or not (so I imagine,...
The current OAS 3.1 spec allows the use of $ref for "Path Item Object" but not for "Operation Object". Is there a reason for this? It would be quite nice...
I am working on using Swagger to define my API's that are complying with the JSON-API spec. It would be helpful if there was a way to wrapper the defined...
https://spec.openapis.org/oas/v3.1.0#fixed-fields-16
Suppose I have the following XML: ``` xml a-b ``` I this the correct way to represent this using Swagger Schema objects? ``` yaml --- type: "object" xml: name: "location"...
## I suggest - OAS 3.1 can reference https://www.ietf.org/archive/id/draft-ietf-httpapi-yaml-mediatypes-01.html#name-yaml-and-json once it's released ## Because - The "YAML JSON Schema" has some issues with inf/nan that do not map to JSON...
In my request model, I have a field like ``` @NotNull @Schema(description = "blahblah", example = "19680228", type = "Date", format = "String", pattern = "([0-9]{4})(?:[0-9]{2})([0-9]{2})", required = true, nullable...
