react-luna-form 0.0.88 → 0.0.89

package/docs/fields/list.md

@@ -25,6 +25,7 @@ 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.
 - **`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).

package/docs/setup.md

@@ -16,7 +16,7 @@ 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`          |
+| `zod`                | `^4.0.6`  | the schema derived from `sections`          |
 | `jotai`              | `^2.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 |
@@ -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.89",
   "description": "A React library for building forms based on JSON",
   "main": "./dist/client/cjs/index.js",
   "module": "./dist/client/esm/index.js",
@@ -26,10 +26,10 @@
     "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.89",
     "@types/react": "19.3.0",
     "@types/react-dom": "19.3.0",
     "eslint-plugin-react": "7.37.5",