react-luna-form 0.0.88 → 0.0.90

package/docs/fields/input.md

@@ -54,7 +54,7 @@ The `advanced` property dictates finer HTML details, interactive structures, and
 
 These basic field types support extra manipulation properties inside the `advanced` block:
 
-- **`length`** _({ min?: number, max?: number })_: Applies HTML structural limits (`minlength` / `maxlength`, or `min` / `max` depending on the input type). On an `input/date` the bounds are days instead; see [The first and the last day](#the-first-and-the-last-day).
+- **`length`** _({ min?: number, max?: number })_: Applies HTML structural limits (`minlength` / `maxlength`, or `min` / `max` depending on the input type). Each bound is a number, or a `$ref` the host resolves to one; see [A bound that is no number](#a-bound-that-is-no-number). On an `input/date` the bounds are days instead; see [The first and the last day](#the-first-and-the-last-day).
 - **`step`** _(number)_ (`input/number` only): A number is whole unless it declares a step, which is the browser's own default of 1. The step is rendered on the input, so its arrows move by it, and validation accepts only values on it, counted from `length.min` when there is one, as the browser does: `0.01` for a price, `0.5` for halves, `0.001` for three decimals. A step has to be a number above 0. The browser ignores 0 and below, and so does the form; text such as `"any"` is no step either, and it is never rendered. Either way the number stays whole.
 - **`transform`** _(string | string[])_: Safely intercepts user inputs and manipulates content dynamically. Options include:
   - `"lowercase"`
@@ -66,6 +66,22 @@ These basic field types support extra manipulation properties inside the `advanc
 
 A required `input/number` accepts `0` and negative numbers: required means a value is present, not that it is at least 1. An optional one left empty is not submitted at all, rather than submitted as `0`, and its `length` bounds only apply to a value that is there. `select/year` and `select/month` read an empty selection the same way.
 
+### Empty and required text
+
+A text left empty is no value for its `length` bounds to check, as the browser's `minlength` does not apply to an empty value either. An optional field left empty, or holding only spaces, passes as `""`, whatever its `length.min`. A required one left empty asks for a value with `validation.required`, not with `validation.length.min`, and its bounds only apply once there is text. This holds for `input/text`, `input/tel`, `input/password`, a [`textarea`](#textarea), and a type the form does not know, which it checks as text.
+
+### A bound that is no number
+
+On the types above, on a [`textarea`](#textarea), and on a type the form does not know, which it checks as text, a `length` bound is a number. A day such as `"2026-10-05"` is not one, nor is text that reads as one, such as `"3"`, nor a `$ref` the context does not hold or holds as `undefined`. Such a bound is a rule the form cannot read, so the field takes no value: anything in it is held back with `This value cannot be checked`, whatever else the field would have checked, such as the address of an `input/email` or the `step` of a number. An optional field left empty still passes, and a required one still asks for a value.
+
+That is deliberate, as it is for [a date](#the-first-and-the-last-day): a server that validates with `buildFormSchema` and forgets its `context` would otherwise let through what the bound was there to keep out, with nothing in production to say so. The input is not handed such a bound, and a development build names it in the console, in the browser and on the server alike, once for each field:
+
+```text
+[Luna Form] when: advanced.length.min is "2026-10-05", which is no number, so the field takes no value
+```
+
+A minimum above the maximum, which no value passes, is named the same way.
+
 ### Temporal Options (`input/date`, `input/time`)
 
 Date and time inputs omit transformations and instead expose a `format` property directly under `advanced` for displaying values properly:
@@ -251,7 +267,7 @@ The `validation` object resolves form errors overriding generic defaults, mappin
 - **`required`** _(string)_: Specifies the error message exposed when the element is marked exactly as `required: true` and the field is empty.
 - **`email`** _(string)_: Error message specifically asserting an invalid email format.
 - **`date`** _(string)_: `input/date` only. The message shown when the field holds text that is no day. Without it, the message is `Invalid date`.
-- **`length`** _({ min?: string, max?: string })_: Specific string messages shown when a value breaches `advanced.length`: a text too short or too long, a number out of range, a day before the first or after the last.
+- **`length`** _({ min?: string, max?: string })_: Specific string messages shown when a value breaches `advanced.length`: a text too short or too long, the address of an `input/email` included, a number out of range, a day before the first or after the last. An address that is no address and is out of its bounds shows both messages, the `email` one first. An optional `input/email` left empty still passes.
 - **`reserved`** _(string)_: `input/date` only. The message shown for a day its `advanced.reserved` lists. Without it, the message is `This date is not available`.
 - **`range`** _(string)_: `input/date` ranges only. The message shown for a range with an end missing, or whose last day comes before its first. Without it, the message is `Invalid date range`.
 - **`step`** _(string)_: The message shown when an `input/number` is off its step: a decimal on a number that declares no step, or a value off the `advanced.step` it declares. The form's dictionary translates it, as it does every other message.
@@ -325,7 +341,10 @@ Everything else in `advanced` is ignored for this type.
 ```
 
 `length.min` and `length.max` are emitted as the `minLength` and `maxLength`
-attributes on the rendered element.
+attributes on the rendered element, and validation checks the same bounds on
+text that is there: see [Empty and required text](#empty-and-required-text). A
+bound that is no number is neither: see
+[A bound that is no number](#a-bound-that-is-no-number).
 
 Like the `input/*` family, a declared `change` event on a `textarea` is
 debounced: it fires 300 ms after the last keystroke, not on every one.

package/docs/fields/list.md

@@ -25,8 +25,11 @@ The `advanced` property customizes structural interaction rules and layout rende
   A custom label has to be translated by the form; the built-in `Add item` default is already translated by the library — see [Localization](#localization).
 - **`length`** _({ min?: number, max?: number })_: Configures restrictions on how many items can be generated. Enforces boundary conditions where minimum instances ensure permanent default items and maximum instances automatically disable insertion toggles. The matching error messages are declared under the list's `validation.length` — see the [Validation reference](../validation/overview.md#list-length).
   Both bounds apply to the rows a list opens with, not only to the ones added by hand: an initial `value` shorter than `min` leaves the remainder standing and empty, and one longer than `max` stops at `max`. A [`value` event](../events/change.md#targeting-a-list) assigning rows is clamped the same way.
+  Each bound is a number, or a `$ref` the host resolves to one. A bound that is not, such as a `$ref` the context does not hold, is a rule the form cannot read: the list is held back with `This list cannot be checked`, an empty one included, since a list has no `required` of its own and `length.min` is how it asks for rows. Meanwhile it shows its rows as if that bound were not declared, a `min` of one or no `max` at all, and a development build names the bound in the console, as it does [for a field](input.md#a-bound-that-is-no-number).
 - **`collapsed`** _(boolean)_: When enabled, list items default to a visually collapsed representation upon mounting or adding.
   Collapsing only hides a row: its fields keep their values, still validate and are still submitted, and a submit that fails on one of them opens the row so the error can be seen.
+- **`fixed`** _(boolean)_: The list keeps the rows it has. It renders no add button and no remove control, and every row stays editable. Reach for it when the rows are created somewhere else and this form only corrects them.
+  It says nothing about how many rows are valid: that is still `length`, read the same way by the schema, and the rows a list opens with are still clamped to `min`. A fixed list that opens with no rows needs `"length": { "min": 0 }`, or it opens with an empty one it cannot remove.
 - **`keepValue`** _(boolean)_: If `true`, hiding the list leaves the values behind instead of taking them. A list holds nothing under its own name, so declaring it here is a statement about the rows: it covers every value they hold. See [Keeping a value through a hide](../events/change.md#keeping-a-value-through-a-hide).
 
 ### Collapsed Previews (`preview` object)
@@ -42,6 +45,7 @@ Previews can map seamlessly pointing out the desired child `name` simply as stri
 
 - **`field`** _(string)_: The child layout field name.
 - **`label`** _(string)_: Provides contextual prefix naming before mapping the preview value statically.
+- **`scope`** _(`"parent"`)_: Reads `field` from the row that holds this list rather than from the row being previewed, one level up. A nested list's rows can then name the outer row they belong to, such as the section a question sits in. In a top-level list there is no row above, and the entry is left out of the preview.
 - **`when`** _(string | string[] | Condition)_: Standard complex logical operators dictating runtime evaluation rules. When an **array** is provided, it performs an **OR match** against the field's current value.
 
 ---

package/docs/setup.md

@@ -16,8 +16,8 @@ dependency, so your application resolves one copy of React, Zod and the rest.
 | Peer                 | Version   | Used for                                    |
 | -------------------- | --------- | ------------------------------------------- |
 | `react`, `react-dom` | `^19.0.0` | rendering, and `useActionState` on submit   |
-| `zod`                | `^4.0.0`  | the schema derived from `sections`          |
-| `jotai`              | `^2.0.0`  | the value, error and source stores          |
+| `zod`                | `^4.0.6`  | the schema derived from `sections`          |
+| `jotai`              | `^3.0.0`  | the value, error and source stores          |
 | `swr`                | `^2.0.0`  | fetching a field's remote `source`          |
 | `date-fns`           | `^4.0.0`  | date and time formatting, `duration` filter |
 | `fast-equals`        | `^6.0.0`  | change detection in the stores              |
@@ -29,6 +29,10 @@ them in for you; anywhere else, install them alongside the library. A missing
 peer surfaces as a module resolution error at import time, not as a form that
 renders badly.
 
+Zod has to be 4.0.6 or later. An earlier 4.0 reports a value that an optional
+text or email field holds back as `Invalid input`, instead of with the field's
+own message.
+
 ## Styling
 
 The components render Tailwind utility classes and **the build ships no CSS**.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-luna-form",
-  "version": "0.0.88",
+  "version": "0.0.90",
   "description": "A React library for building forms based on JSON",
   "main": "./dist/client/cjs/index.js",
   "module": "./dist/client/esm/index.js",
@@ -21,15 +21,15 @@
   "peerDependencies": {
     "date-fns": "^4.0.0",
     "fast-equals": "^6.0.0",
-    "jotai": "^2.0.0",
+    "jotai": "^3.0.0",
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
     "swr": "^2.0.0",
     "tailwind-merge": "^3.7.0",
-    "zod": "^4.0.0"
+    "zod": "^4.0.6"
   },
   "devDependencies": {
-    "@luna-form/core": "0.0.88",
+    "@luna-form/core": "0.0.90",
     "@types/react": "19.3.0",
     "@types/react-dom": "19.3.0",
     "eslint-plugin-react": "7.37.5",