swaggerize-routes
swaggerize-routes copied to clipboard
krakenjs
Swagger document driven route builder.
Prior to making the parameter validators, an object is created where the object property keys are built from the parameters `in` and `name` properties. However, these properties are not existent...
Example: ... ``` ... put: parameters: - name: body required: true in: body schema: $ref: '#/definitions/employeeFull' ``` validator.js does not call $ref resolution before enjoi at line 97. Suggested fix:...
Hey, can you please update enjoi to the latest version? There is a known vulnerability in one of the dependencies which should be updated: Is this project still maintained in...
In swaggerize-express, I found that validation is not performed (enums, lengths, required fields) on parameters that are referenced ($ref) in a path (instead of inline). The updated code ensures that...
Errors thrown by `require(pathname)` were previously caught and suppressed here with a wrong messsage to debuglog. Since this is also the code that includes security middlewares, errors should be thrown.
Add an option for a default (fallback) handler to be used if no other handler was found or given: - Default handler is optional. - Handler must be a function....
A result of `fs.readdirSync(dir)` is important because it could create error when the order of directory name precede filename. for example, let's assume that there is two files. handlers/users.js handlers/users/{userId}.js...
If a validation error happens, I would like to know the location of the parameter. e.g.`header`, `query`, `path`, `body`. Also I would like the `context.key` to have the right key...