ata-validator

validateJSON() returned a bare false instead of a result for an invalid document when any string in the schema contained the word function, such as a property named function. Code that checks if (!result.valid) behaved correctly, but reading result.errors threw, and a check written as result.valid === false let the document through. The generated code is rewritten as text to build that path, and the rewrite read the word inside a string as the start of a function. Strings are now skipped. Affected: 1.23.0 to 1.41.0. validate(), isValidObject() and isValidJSON() were not affected. tests/test_generated_returns_rewrite.js puts the words and characters that rewrite looks for into property names, enum values and patterns, and checks every entry point against the interpreted engine.

A uniqueItems error named a different duplicate pair depending on the engine that answered. Every engine now reports the first item that has a later equal, and its first later equal (params: { i, j }), as the interpreted engine did. The message for a document checked by generated code can name a different pair than before.

Generated code and the interpreted engine gave different error lists for the same document in a few shapes; what is accepted did not differ. A value of the wrong type is now also checked against the keywords that apply to its own type (minimum for 2.5 against type: "integer", allOf and if for null against type: "object"), a collapsed oneOf or anyOf under a pattern sorts in schema order, and type written as a one-element array is reported as an array. The SchemaStore sample documents, 31080 of them with mutated copies, now get identical error lists from both engines; three differed before.

An isValidObject taken before the validator's first call, as in const check = v.isValidObject, classified the schema again on every call, about ten times the cost of the check. It now hands straight to the compiled check.