express-openapi-validate
express-openapi-validate copied to clipboard
Hilzu
Express middleware to validate requests based on an OpenAPI 3 document
If an express route includes any path parameters (/foo/:bar, which the swagger represents as /foo/{bar}), and the match middle ware is configured, when the OpenAPIValidator validate method is called, the...
Hello, i have a problem: my openapi spec has circular reference, so i am getting `Maximum call stack size exceeded` because of it in `walkSchema` function of schema-utils.js. Is there...
The code path implicated in the memory leak is this usage of this.validate inside the middleware that is returned by match, because this.validate internally is calling ajv's compile. https://github.com/Hilzu/express-openapi-validate/blob/cb699f7ec5df995b9399bc671bdf0188659fb1e7/src/OpenApiValidator.ts#L170 Per...
Improved SchemaObject interface. Many of its properties can be of type ReferenceObject per OpenAPI specification. # Issue Currently OpenAPI document that makes use of `$ref` in SchemaObjects do not pass...
Error: unknown format "uuid" ignored in schema at path "#/properties/params/properties/entity_uuid"
0.6.0/0.6.1 does not work with format: uuid. Worked in 0.4.4 just fine. Are ajv formats being used properly?
Swagger 2.0 supports form data validation, but I had an issue with `express-openapi-validate`. It throws the following error: ``` Error: Unrecognized parameter location=formData at parameterLocationToRequestField (/usr/src/app/node_modules/express-openapi-validate/dist/parameters.js:32:11) ``` In [./src/parameters.ts](https://github.com/Hilzu/express-openapi-validate/blob/master/src/parameters.ts#L39), we...
I'm getting the following error for request validation: > error while validating request: request should have required property '.headers' The stack I am using is: - express 4.17.1 - express-openapi-validate...
Teamwork
Hey there! It looks like you and https://github.com/Zooz/express-ajv-swagger-validation are working on the same thing. Maybe you folks could join forces and share the load.
It doesn't look like validating parameters that are passed like this is supported: ``` parameters: - in: query name: filter required: true schema: type: object properties: petid: type: integer example:...
Hello, It seems that we are unable to detect extra parameters in the query of a request. For example: GET /pets?foo=bar passes without error even if the parameter "foo" is...
