@jarenjs/forms 0.34.2 → 0.43.1

package/README.md

@@ -6,7 +6,7 @@ Framework-agnostic form generation for JSON Schema. Turns a schema into a render
 2. **Cross field, every keystroke** — visibility, enablement, computed values, and preemptive assertions expressed as [Jaren JSON Query](../json/docs/QUERY-FORMAT.md) documents in an `x-form` annotation, compiled once per model by [`@jarenjs/json`](../json) and evaluated per keystroke as cheap closures.
 3. **Authoritative, on submit** — the complete compiled schema validation with [`@jarenjs/validate`](../validate), which owns `required` combinations, `dependentSchemas`, `if/then/else`, `unevaluatedProperties`, and (via the `$query` keyword) the very same cross-field rules.
 
-No DOM, no framework: render the model with React, Vue, vanilla JS or anything else. Forms never imports the validator — apps wire the authoritative layer themselves. See it in action in the [Jaren playground](https://jklarenbeek.github.io/jarenjs/#/playground).
+No DOM, no framework: render the model with React, Vue, vanilla JS or anything else. Forms never runs the validator — apps wire the authoritative layer themselves; the only thing it imports from `@jarenjs/validate` is the pure same-document `$ref`/`$anchor` resolution in `@jarenjs/validate/normalize`. See it in action in the [Jaren playground](https://jklarenbeek.github.io/jarenjs/#/playground).
 
 ## Usage
 

package/dist/types/index.d.ts

@@ -6,7 +6,9 @@
  * primitives, and the `x-form` rules (rules.js) add cross-field behavior -
  * visibility, enablement, computed values, preemptive assertions - as
  * compiled Jaren JSON Queries, before the complete compiled schema
- * validation runs (app-wired; forms never imports the validator). The
+ * validation runs (app-wired; forms never RUNS the validator — its one
+ * import from that package is the pure same-document ref resolution in
+ * `@jarenjs/validate/normalize`). The
  * data helpers keep form values in plain JSON semantics, addressed by
  * JSON pointer through the @jarenjs/json compiled pointer engine.
  */

package/dist/types/rules.d.ts

@@ -74,8 +74,8 @@ export type CompiledRules = {
  * document. `options.compileTypeTest` passes through to the query
  * compiler, so rules may use `$valid`/`$assert`/`$as` with a
  * caller-supplied type-test compiler (the validator package's `query`
- * module exports `createTypeTestCompiler()`; forms itself never imports
- * the validator).
+ * module exports `createTypeTestCompiler()`; forms itself never runs
+ * the validator, and imports only its pure `normalize` helpers).
  * Without the hook, a schema-using rule surfaces the engine's JQ0008.
  *
  * @param {import('./model.js').FormField} model - Root field from buildFormModel

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jarenjs/forms",
   "private": false,
-  "version": "0.34.2",
+  "version": "0.43.1",
   "type": "module",
   "main": "./src/index.js",
   "types": "./dist/types/index.d.ts",
@@ -47,9 +47,9 @@
     "prepack": "npm run build:types"
   },
   "dependencies": {
-    "@jarenjs/core": "^0.34.2",
-    "@jarenjs/formats": "^0.34.2",
-    "@jarenjs/json": "^0.34.2",
-    "@jarenjs/validate": "^0.34.2"
+    "@jarenjs/core": "^0.43.1",
+    "@jarenjs/formats": "^0.43.1",
+    "@jarenjs/json": "^0.43.1",
+    "@jarenjs/validate": "^0.43.1"
   }
 }

package/src/index.js

@@ -8,7 +8,9 @@
  * primitives, and the `x-form` rules (rules.js) add cross-field behavior -
  * visibility, enablement, computed values, preemptive assertions - as
  * compiled Jaren JSON Queries, before the complete compiled schema
- * validation runs (app-wired; forms never imports the validator). The
+ * validation runs (app-wired; forms never RUNS the validator — its one
+ * import from that package is the pure same-document ref resolution in
+ * `@jarenjs/validate/normalize`). The
  * data helpers keep form values in plain JSON semantics, addressed by
  * JSON pointer through the @jarenjs/json compiled pointer engine.
  */

package/src/rules.js

@@ -181,8 +181,8 @@ function compileRuleMessageSpec(raw, fieldPointer) {
  * document. `options.compileTypeTest` passes through to the query
  * compiler, so rules may use `$valid`/`$assert`/`$as` with a
  * caller-supplied type-test compiler (the validator package's `query`
- * module exports `createTypeTestCompiler()`; forms itself never imports
- * the validator).
+ * module exports `createTypeTestCompiler()`; forms itself never runs
+ * the validator, and imports only its pure `normalize` helpers).
  * Without the hook, a schema-using rule surfaces the engine's JQ0008.
  *
  * @param {import('./model.js').FormField} model - Root field from buildFormModel