Pavel Akulich
Pavel Akulich
If it compiled with the node v0.10, then there is no error
if compiled OK and then run under the node v.0.12 it's allright
JSON.parse does not worry about it) It need to handle manually and causes the performance issues. May be some people don't know about the **proto** property behaviour in the js...
It's may used for any hacks. Many peoples use Object.keys for validation objects, that have been parsed by JSON, and as you know Object.keys does not returns properties from the...
"It's very unusual to have **proto** into JSON feeds. It should be stripped by serialization" Yes it should be stripped by serialization, but if a malefactor has made a JSON...
``` javascript var oo ='{"prop1":"val1","__proto__" : { "hasOwnProperty":"true", "toString" : "ok" }}'; var jsO = JSON.parse(oo); console.log(jsO.toString); ``` the result is "ok"
Yes, but even this implementation of the asynchronous validation may help to many peoples like me, and it have another features
I've compared the performance of my fork and your code. It seems to be on a par
And the async validation may be the main benefit of this library against the library is-my-json-valid
You have the bug with a custom patterns and the predefined formats: var jsen = require("jsen"); var obj1 = { date : 2 }; var schema = { type :...