@jarenjs/forms 0.49.2 → 0.56.0

package/README.md

@@ -21,13 +21,13 @@ import {
 
 const schema = {
   type: 'object',
-  title: 'Sign up',
   properties: {
     username: { type: 'string', minLength: 3, pattern: '^[a-z0-9_]+$' },
     email: { type: 'string', format: 'email' },
     age: { type: 'integer', minimum: 13 },
   },
   required: ['username', 'email'],
+  title: 'Sign up',
 };
 
 // 1. Build the field tree once
@@ -90,6 +90,27 @@ stylesheet is the second kind of host, and the website's data studio the first.
 
 Which date formats get a **native** control is decided by the offset, not by convenience. HTML's `datetime-local` and `time` inputs cannot produce one, and RFC 3339 requires one — binding them to `date-time`/`time` would make the control emit values its own schema rejects, so those stay text inputs. The `iso-date-time`/`iso-time` formats leave the offset optional and are exactly what those inputs spell, so they map losslessly. `formatMinimum`/`formatMaximum` reach the field as constraints and become the control's `min`/`max`, so the picker itself refuses an out-of-range date; HTML has no exclusive date bounds, so `formatExclusive*` stays a submit-time check.
 
+### The same model, by code
+
+The schema above is what `@jarenjs/linq/forms` emits, byte for byte:
+
+```javascript
+import * as f from '@jarenjs/linq/forms';
+
+export const signup = f.object({
+  username: f.string().min(3).pattern('^[a-z0-9_]+$'),
+  email: f.string().format('email'),
+  age: f.integer().min(13).optional(),
+}).open().title('Sign up');
+
+const model = buildFormModel(signup.schema);
+```
+
+Every rule of the next section is a `.form({ … })` on the member it
+belongs to; the pen's document is
+[FORMS-PEN.md](../linq/docs/FORMS-PEN.md), and nothing in this package
+depends on it — the schema is the contract.
+
 ## Layer 1 — preemptive per-field validation
 
 `validateField(field, value)` returns `[{ keyword, message }]` using `@jarenjs/core` directly:
@@ -119,6 +140,16 @@ One namespaced annotation keyword — safe under every metaschema, invisible to
   } }
 ```
 
+These annotations can be **written by code**: `@jarenjs/linq/forms` is
+the schema pen plus `form({ visible, enabled, assert, computed,
+message })` on every builder, with the rules captured as callbacks over
+the same context (`c.root`, `c.value`, `c.pointer`) rather than typed
+as path strings, and `assertOnSubmit()` answering the layer-3 twin
+below in one call. The document above is what it emits, byte for byte
+— see [the by-code twin](#the-same-model-by-code) and
+[FORMS-PEN.md](../linq/docs/FORMS-PEN.md). This package depends on
+none of it; the annotation is the contract.
+
 Recognized members — unknown members are ignored for forward compatibility:
 
 | Member | Kind | Meaning |

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jarenjs/forms",
   "private": false,
-  "version": "0.49.2",
+  "version": "0.56.0",
   "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.49.2",
-    "@jarenjs/formats": "^0.49.2",
-    "@jarenjs/json": "^0.49.2",
-    "@jarenjs/validate": "^0.49.2"
+    "@jarenjs/core": "^0.56.0",
+    "@jarenjs/formats": "^0.56.0",
+    "@jarenjs/json": "^0.56.0",
+    "@jarenjs/validate": "^0.56.0"
   }
 }