ata-validator
1.61.3 · 29 Oct 2026MIT21.8k / weekRepositoryHomepagenpmAtom feed
1.61.3 is the newest release of 1.x.
In short
4 changed
Release note
Changed
Errors are put in schema declaration order by an integer computed when the schema is compiled, not by walking each error's schemaPath at read time. The rank of a path is its pre-order position in the schema tree, which is exactly the order the old array-of-indexes comparison produced; the code generator writes that position into each error literal (
_o, an internal field), the reader compares integers, and a list that already arrives in order is returned without sorting or allocating.The Standard Schema bridge caches parsed issue paths per instancePath string (bounded, entries frozen).
Measured on the schema-benchmarks harness locally, before and after on the same machine: standard invalid 3.57 to 2.83 µs (21 percent less); every other row within noise. Raw error list of that schema, 15 errors: 1.88 to 1.50 µs; through the Standard Schema bridge 3.30 to 1.99 µs. Verdict paths are untouched.
richErrors: falsekeeps the v0.14 key set: the ordering field is dropped from that shape.
Suite: Draft 2020-12 1299 of 1299, draft 7 927 of 927, v1 1133 of 1133.