formstand 0.4.1 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,123 @@
 # Changelog
 
+## 0.6.0 — 2026-07-09
+
+### Added
+
+- `useIsDirty(form, path?)` and `useIsValid(form, path?)`: an optional
+  typed path scopes the flag to a subtree with the library's usual prefix
+  semantics (`"shipping"` covers `shipping.city`; for validity the path's
+  own key counts, so array-level errors match their array's path).
+  Subscriptions stay boolean-only — the component re-renders when the flag
+  flips, not on every keystroke like `useField(...).dirty`. Omitting the
+  path keeps the whole-form behavior; schema-less `FieldFormApi`-style
+  forms take plain string paths.
+
+## formstand-cli 0.2.2 — 2026-07-09
+
+- Generated array hooks drop the explicit item type
+  (`useFieldArray(form, "items")`): formstand ≥ 0.5 infers it from the
+  schema through the path — and rejects the old explicit spelling on typed
+  forms. On formstand 0.4 the generated code still compiles, with untyped
+  items.
+- Generated shadcn output defines one `ariaInvalid` helper (used by the
+  inlined adapters and the select trigger) instead of repeating the ternary
+  four times, and the generated `FieldError` computes the message once —
+  cosmetic; runtime behavior unchanged. Internally the MUI and shadcn
+  backends now share their emitted snippets (error helper, `BoundFieldProps`,
+  the leaf switch), so the generators can't drift.
+
+## 0.5.0 — 2026-07-09
+
+### Breaking
+
+- `useFieldArray` infers the item type from a `Form<TSchema>` and a typed
+  path — `useFieldArray(form, "users")` (and template paths like
+  `` `albums.${index}.tracks` ``) needs no type argument, and `push`/`insert`
+  are typed against the schema's item. Consequently the old explicit
+  `useFieldArray<TItem>(form, path)` spelling is a **compile error on typed
+  forms** (drop the generic); it remains the way to bind schema-less
+  `FieldFormApi` forms, where there is nothing to infer from. A non-array
+  path types the items as `never`; a typo'd path is rejected against the
+  full `FieldPath` union, like `useField`. Path selectors return
+  `UseFieldArrayReturn<unknown>` (dynamic paths carry no type), also like
+  `useField`.
+
+### Fixed (site only)
+
+- The deployed playground bundled two copies of React (the formstand alias
+  reaches outside the examples package, so its imports resolved the repo
+  root's copy) — every tab crashed at startup with a null hooks
+  dispatcher. The examples build now dedupes react/zustand/zod and CI
+  asserts the bundle holds exactly one React.
+
+### Docs & examples (no package changes)
+
+- The playground demos bind shadcn's `Input`/`Textarea` with the library's
+  own exported `textInputProps`/`numberInputProps` — the shadcn adapter now
+  covers only the Radix dialect, and the "field has an error" predicate
+  lives once in `examples/src/fieldErrors.ts` (shared by both adapters).
+- The copy-in shadcn kit is trimmed to what the demos render (Badge/Button
+  variants, dead peer-disabled label classes) and every component exports a
+  `Readonly` props type.
+
+## formstand-cli 0.2.1 — 2026-07-09
+
+### Fixed
+
+- Leaf-free schemas (no scalar fields anywhere, e.g. an object of empty
+  objects) no longer generate non-compiling output in the `mui` and
+  `shadcn` backends — the emitted `BoundFieldProps` type referenced
+  `FieldFormApi` without importing it. All three backends now have a
+  leaf-free typecheck test.
+- The shadcn backend's generated output is additionally typechecked in CI
+  against the repo's real Radix-based components (not just the structural
+  stub), so a shadcn/Radix prop-contract change fails our suite instead of
+  the consumer's build.
+
+### Docs & examples (no library package changes)
+
+- Playground: the page chrome stylesheet is unlayered again — cascade
+  layers can't be transpiled, so pre-15.4 WebKit (the es2019 target's
+  audience) was losing every tab's styling; its selectors are class-scoped,
+  so the shadcn utilities are unaffected. The layer-order statement now
+  pins Tailwind's canonical `components` slot below `utilities`.
+- shadcn kit: sliders take an `aria-label` routed to the Radix Thumb (the
+  Root is a `<span>`, so `htmlFor`/`id` never named it); radio-group items
+  show error styling via `group-aria-invalid` (Radix doesn't propagate the
+  Root's `aria-invalid` to items); the Team demo's rows are memoized with
+  stable handlers so keystrokes in one row stop re-rendering the rest.
+- Publish workflow: `--provenance` is explicit again (fail-closed — the
+  automatic path silently skips attestation when conditions aren't met) and
+  the Node pin is `>=24.8`, the first line whose bundled npm meets trusted
+  publishing's 11.5.1 floor. CI asserts the root and examples lockfiles
+  agree on the deduped UI packages, so the smoke test can't silently
+  certify a different build than the deployed playground.
+
+## formstand-cli 0.2.0 — 2026-07-08
+
+### Added
+
+- `--ui shadcn`: generates forms against [shadcn/ui](https://ui.shadcn.com/)
+  conventions — components imported from the app's `@/components/ui/*` alias
+  (what `npx shadcn add` scaffolds), an inlined adapter speaking the Radix
+  dialect (`onCheckedChange`/`onValueChange`, dropdown-close as the blur
+  trigger), and `aria-invalid` error styling with a message line. Generated
+  output is typechecked in CI against the library source and a structural
+  stub of the shadcn components, like the other backends.
+- `emitShadcnForm` joins the programmatic API.
+
+### Docs & examples (no library package changes)
+
+- Four shadcn/ui playground demos (Signup, Checkout, Settings, Team) plus
+  the formstand→shadcn adapter pattern they showcase —
+  `examples/src/shadcn/shadcnAdapter.ts` bridges `useField` to both native
+  inputs and the Radix-based widgets (Checkbox, Switch, Select, Slider,
+  RadioGroup).
+- The playground carries its own copy-in shadcn component kit under a
+  scoped Tailwind 4 setup (no preflight; the plain-CSS and MUI demos are
+  untouched).
+
 ## 0.4.1 — 2026-07-08
 
 ### Fixed

package/dist/index.cjs

@@ -995,17 +995,26 @@ var useFormError = (form) => react$1.useStore(
   form.store,
   shallow.useShallow((state) => state.errors[""])
 );
-var useIsDirty = (form) => react$1.useStore(
-  form.store,
-  (state) => isFieldDirty(state.values, state.initialValues)
-);
-var useIsValid = (form) => react$1.useStore(form.store, (state) => {
-  for (const k in state.errors) {
-    const errs = state.errors[k];
-    if (errs !== void 0 && errs.length > 0) return false;
-  }
-  return true;
-});
+function useIsDirty(form, path) {
+  return react$1.useStore(
+    form.store,
+    (state) => path === void 0 || path === "" ? isFieldDirty(state.values, state.initialValues) : isFieldDirty(
+      getAtPath(state.values, path),
+      getAtPath(state.initialValues, path)
+    )
+  );
+}
+function useIsValid(form, path) {
+  return react$1.useStore(form.store, (state) => {
+    for (const k in state.errors) {
+      const errs = state.errors[k];
+      if (errs !== void 0 && errs.length > 0 && (path === void 0 || path === "" || isPathOrChild(k, path))) {
+        return false;
+      }
+    }
+    return true;
+  });
+}
 var useIsSubmitting = (form) => react$1.useStore(form.store, (state) => state.isSubmitting);
 var useSubmitCount = (form) => react$1.useStore(form.store, (state) => state.submitCount);
 function useField(form, pathArg, options) {
@@ -1429,7 +1438,7 @@ var reconcileIds = (prev, nextItems) => {
     counter: prev.counter + Math.max(0, unmatched - leftover.length)
   };
 };
-var useFieldArray = (form, pathArg) => {
+function useFieldArray(form, pathArg) {
   const path = react$1.useStore(
     form.store,
     (state) => typeof pathArg === "function" ? pathArg(state) : pathArg
@@ -1494,7 +1503,7 @@ var useFieldArray = (form, pathArg) => {
     }),
     [fields, items, error, push, remove, insert, move, swap]
   );
-};
+}
 
 exports.CheckboxField = CheckboxField;
 exports.NumberField = NumberField;