-
Some suggestions for additional rules: If OAuth is used, an `authorizationUrl`, `tokenUrl` (depending on the OAuth flow) and a `refreshUrl` as well as `scopes` should be specified (see https://swagger…
-
### Q&A (please complete the following information)
- OS: Windows 7
- Browser: Firefox 70.0.1
- Version: Swagger editor (online version)
- Method of installation: no installation
- Swagg…
-
### Project
API (api.potterdb.com)
### Describe the feature you want to request
Self-explanatory Swagger that would not necessarily replace but extend existing GraphQL and REST API documentat…
-
"Any Type" is part of the specification ( https://swagger.io/docs/specification/data-models/data-types/#any ), however this library does not support it.
The problem seems that, when creating the `S…
-
## Problem statement
I have 2 interrelated questions
1)
Is it possible to add the reason for the error within the swagger:route annotation where we define the list of responses?
```
// swagge…
-
Currently, definitions can be registered to be referenced to in the spec.
The spec allows to register other objects like parameters or responses.
OpenAPI 3: https://swagger.io/specification/#com…
-
Hi,
Would it be possible for you to point me in the direction of how to do a couple of things with this library, to validate an api against a swagger schema.
i) Can I validate my generated swagg…
-
This issue is related to #696.
However openapi 3.0 specification says `exclusiveMinimum` and `exclusiveMaximum` should be boolean.
They became numbers in openapi 3.1.
`open-api-validator` shoul…
-
When generating C# client code with the NSwag command line toolchain 13.9.2 Netcore31 from
root.yaml:
```
openapi: 3.0.2
paths:
/test:
$ref: './path.yaml#/paths/test'
```
path.yam…
-
Currently the specs are Word/PDF documents, probably hand written. This is very error prone for the authors, leads to inconsistencies we can see in the current versions.
For the spec user such as ban…