node-restify-validation
node-restify-validation copied to clipboard
z0mt3c
Validation for REST Services built with node-restify in node.js
**Description** - Upgrade lodash version to `v4` - Fixes - https://github.com/z0mt3c/node-restify-validation/issues/86
I'm busy for a long while, then I can't assume the maintenance of this project. Moreover, I don't work anymore with node js technology. If someone want to take lead...
All validation rules are completely ignored using Restify 7.x.x. Rolling back to Resitfy 6.4.0 resolves the issue for me, and everything works as before. I'm running this on Node 8.9.0
## Overview `npm audit` command is reporting some lodash vulnerabilities for this module. ## Vulnerabilities |module|path|recommended version|overview|more info| |-|-|-|-|-| |lodash|node-restify-validation > lodash|4.17.12|Prototype Pollution|https://nodesecurity.io/advisories/1065| |lodash|node-restify-validation > lodash|4.17.11|Prototype Pollution|https://nodesecurity.io/advisories/782| |lodash|node-restify-validation > lodash|4.17.5|Prototype...
I am keep getting 409 Conflict ``` { "code": "InvalidArgument", "message": "name (MISSING): Field is required, email (INVALID): Invalid email" } ``` if I am sending data with ``` Content-Type:...
When using this configuration: `validation: { headers: { 'x-app-key': { isRequired: true } } }` A request using the required field works fine: `curl -X POST -H "Content-Type: application/json" -H...
When validation fails, the library used to return a 400 (Bad Request) response. Then this was changed to 409 (Conflict) for some unexplained reason. https://github.com/z0mt3c/node-restify-validation/commit/9ad8c8751ec0be533ebe7cfff03109d76b6a549b#diff-b83d27d3c5374e6d6de83271284db8c4 There doesn't seem to be...
I couldn't figure out how to put up validation with multipart form request.
This is one of the most popular use cases to make sure people dont put names, etc. as an empty string or 1 character. eg: ``` { name: { isRequired:...
