OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
The OpenAPI Specification Repository
I'm running into an issue with the spec. https://github.com/swagger-api/validator-badge/issues/73 It seems that template paths are not allowed in the tokenUrl parameter of security definitions. my use case is: ``` yaml...
Hey all, I did some searching in the OAI repo, and it didn't jump out at me as an existing feature request. The issues with enum being "non-growable" without making...
In the definition of the [License object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#licenseObject) of OpenAPI 3.1: the `url` and `identifier` properties are not marked as REQUIRED, so optional, and are defined as mutually exclusive. The [schema...
Hi, I really like this README document, it gives me a quick overview of the project, and I've changed a few things, which makes the document look clearer and easier...
I don't know it is good place to introduce new Feature into swagger specification - if not please give me information where i can put this proposition. My proposition is...
I see there are a few issues which ask for the opposite, e.g. this one https://github.com/swagger-api/swagger-js/pull/280 , but what I'm asking for is to add some option to the parameter,...
https://github.com/OAI/OpenAPI-Specification/blob/aa91a19c43f8a12c02efa42d64794e396473f3b1/schemas/v3.0/schema.yaml#L211
Hi everybody, not sure if this is the right place to ask this, but I've intercepted an ambiguity while building tooling for OAS 3.1 ```json { "openapi": "3.1.0", "components": {...
