Tags: ata-core/ata-validator
Tags
fix(ci): build macOS x64 on an Intel runner, verify signatures locally macos-14 runners are Apple Silicon only, so the x64 matrix leg built an arm64 binary mislabeled as x64 and no darwin-x64 prebuild reached the tarball. Move that leg to macos-13. Extend the prepublishOnly guard to verify darwin code signatures when publishing from a Mac. Prepare 0.13.4.
fix(validate): keep invalid path on JS-only fallback when native is a…
…bsent
errFn fell through to this._compiled.validate(d) whenever the JS error
codegen probe couldn't produce a safe error function. _ensureNative is a
no-op when the native addon isn't present, so _compiled stayed null and
the invalid path threw "Cannot read properties of null (reading
'validate')" on Workers, browsers, and Bun without N-API. The valid
path was unaffected because it short-circuits before errFn.
Routes the fallback to a JS-only branch when native is absent. Returns
the jsFn boolean with a generic detail-not-available error so callers
see {valid:false, errors:[...]} instead of a crash. Adds
tests/test_no_native.js to exercise the reporter's schema in a sandbox
that blocks pkg-prebuilds resolution.
Fixes #22.
fix(format): wire user formats into the combined codegen path The combined path (compileToJSCombined → validate()) accepted a userFormats argument from the caller but the function signature dropped it before initializing ctx, so schemas with `format: <user-defined>` short-circuited to valid=true regardless of what the checker returned. The boolean (compileToJSCodegen) and error-only (compileToJSCodegenWithErrors) paths were already correct. Adds the missing parameter, threads it through ctx, and emits the same closure-call branch the other paths use.
resolve cross-schema $ref with json pointer fragments bundleStandalone failed when a schema referenced a sibling via "<id>#/<json-pointer>" syntax. The closure resolver, codegenSafe, and all three codegen paths (genCode / genCodeE / genCodeC) now walk the pointer into the host schema.
address rjsf adoption feedback - custom formats via options.formats and addFormat (issue #1) - verbose option populates parentSchema on errors (issue #2) - standard schema path indices emitted as numbers (issue #3) - toStandaloneModule type added to index.d.ts (issue #4) - bundleStandalone: format option ('esm' or 'cjs'), default cjs (issue #5) - bundleStandalone: cross-schema $ref resolution (issue #6)
PreviousNext