torch-glare 2.5.5 → 2.6.0

package/docs/migration/changelog.md

@@ -1,54 +0,0 @@
----
-title: Changelog & Upgrading
-description: How to upgrade copied TORCH Glare components and where to find release notes.
-group: migration
-keywords: [changelog, migration, upgrade, update]
----
-
-# Changelog & Upgrading
-
-## Upgrading in a copy-in library
-
-Because components are **copied into your project**, upgrading is not an `npm update`. To pull
-the latest component source, re-run the CLI:
-
-```bash
-# Re-sync everything already installed with the latest templates
-npx torch-glare@latest update
-```
-
-`update` overwrites your local copies, so review the diff and re-apply any local changes you
-made. To upgrade a single component, re-add it:
-
-```bash
-npx torch-glare@latest add Button
-```
-
-## Release notes
-
-- **v2.5.5** — **breaking**: `DataViews.Filters.Summary` is removed with no shim; delete any
-  `<DataViews.Filters.Summary />` (render your own from `useDataViewsFilters()` if you want one).
-  Also, every `FormBuilder.*` field takes a `hints` array, so one field can
-  carry several alerts. The validation error renders first, your hints follow. See
-  [FormBuilder](../components/form-builder.md#hints). Dropdown panels (`Select`,
-  `SearchableSelect`, `SearchableTree`, `Popover`, `DropdownMenu`, `ContextMenu`) now cap to the
-  space actually on screen and scroll their list in an inner viewport instead of being clipped —
-  note `SearchableTree`'s `maxBodyHeight` default drops 320 → 200, and menu submenus gained a
-  `maxHeight` (they were previously uncapped). `InputField`, `BadgeField` and `Select` no longer
-  pop an error tooltip — an invalid control is shown by its negative border alone, and
-  `toolTipSide` is deprecated and ignored. Plus fixes to `TabSwitch` dividers,
-  `FieldSection` hint placement, the
-  `FormRenderer` stepper grid, `SlideDatePicker` theming and `PopoverItem`'s disabled state.
-- **v2.5.2** — **breaking**: `FormBuilder` now holds only the fields; the section cards, title
-  header and stepper moved to `FormRenderer`. See
-  [FormBuilder 2.5.2](./form-builder-2.5.2.md) for the rename table.
-- **v1.1.16** — see [CHANGELOG-1.1.16.md](../CHANGELOG-1.1.16.md) (adds `TextEditor`,
-  `ChartBlockTool`, and related components).
-
-For the authoritative version, check the `version` field in the package's `package.json` or
-run `npx torch-glare --version`.
-
-## See also
-
-- [CLI reference](../reference/cli.md)
-- [Architecture](../explanation/architecture.md)

package/docs/migration/form-builder-2.5.2.md

@@ -1,113 +0,0 @@
----
-title: FormBuilder 2.5.2 — the chrome moved to FormRenderer
-description: FormBuilder now holds only the fields. The section cards, title header and stepper moved to FormRenderer. What to rename, and why.
-group: migration
-keywords:
-  [migration, breaking, form-builder, form-renderer, section, stepper, header, 2.5.2, upgrade]
----
-
-# FormBuilder 2.5.2 — the chrome moved to FormRenderer
-
-**`FormBuilder` is now the fields and nothing else.** Everything drawn *around* the fields —
-titled section cards, the page title header, the stepper and its rail, the page gutters, the
-scroll shell, the summary column — now lives on [`FormRenderer`](../components/form-renderer.md).
-
-## Why
-
-The split was already documented this way; the code just did not honour it. `FormBuilder` owned a
-`rounded-2xl` page shell, a title header that a *child element* switched on, a stepper rail, and a
-`conclusion` panel rendered outside its own `<form>` — while its own doc comment described it as
-"drawer-unaware". The tell was the `layout="bare"` prop: page framing had been baked in, and
-anything embedding a form (a 260px settings rail, a `DataViews` filter panel) needed an escape
-hatch to turn it off.
-
-Now there is nothing to escape. A bare `<FormBuilder>` renders a `<form>` and your fields, and
-fills whatever it is placed in. `FormRenderer` draws the page.
-
-## What to rename
-
-| Before                  | After                    |
-| ----------------------- | ------------------------ |
-| `FormBuilder.Section`   | `FormRenderer.Section`   |
-| `FormBuilder.Stepper`   | `FormRenderer.Stepper`   |
-| `FormBuilder.Step`      | `FormRenderer.Step`      |
-| `FormBuilder.Back`      | `FormRenderer.Back`      |
-| `FormBuilder.Next`      | `FormRenderer.Next`      |
-| `FormBuilder.Header`    | `FormRenderer`'s `header` prop (see below) |
-
-**`FormBuilder.Submit` does not move.** It is the form's own submit button and still
-auto-associates with the `<form>` by id, so it works from the header action bar as before.
-
-### Two root props are gone
-
-| Removed                     | Replacement                                                        |
-| --------------------------- | ------------------------------------------------------------------ |
-| `layout="page" \| "bare"`    | Nothing — bare is the only behaviour. The 1100px cap and 48px gutters are `FormRenderer`'s. Delete the prop. |
-| `conclusion={<FormSummary/>}` | `FormRenderer`'s `summary` prop.                                   |
-
-`className` now lands on the `<form>` element itself rather than an outer page wrapper. On
-`FormRenderer` it still lands on the outermost element, so `className="min-h-0 flex-1"` behaves
-exactly as before.
-
-### `FormBuilder.Header` → the `header` prop
-
-The header was a child that silently reconfigured the root into a scroll-shell layout. It is now
-a prop, so a child can no longer change the page around it:
-
-```tsx
-// Before
-<FormBuilder onSubmit={save} resolver={r} defaultValues={d}>
-  <FormBuilder.Header title="Item" variant="new">
-    <FormBuilder.Submit>Save</FormBuilder.Submit>
-  </FormBuilder.Header>
-  <FormBuilder.Section title="Identity" color="Blue">
-    <FormBuilder.Text name="name" label="Name" required />
-  </FormBuilder.Section>
-</FormBuilder>
-
-// After
-<FormRenderer
-  onSubmit={save}
-  resolver={r}
-  defaultValues={d}
-  header={{ title: "Item", variant: "new" }}
-  actions={<FormBuilder.Submit>Save</FormBuilder.Submit>}
->
-  <FormRenderer.Section title="Identity" color="Blue">
-    <FormBuilder.Text name="name" label="Name" required />
-  </FormRenderer.Section>
-</FormRenderer>
-```
-
-## Doing the upgrade
-
-There is no compatibility shim: the removed parts are gone, so **TypeScript finds every call site
-for you**. Re-run the CLI, then let the compiler drive:
-
-```bash
-npx torch-glare@latest add FormBuilder FormRenderer --force
-npx tsc --noEmit
-```
-
-Each error is one of the renames in the table above. If a form used raw `FormBuilder` for a real
-page, wrap it in `FormRenderer` — that is where its header, gutters and section cards now come
-from.
-
-### Field layout is unchanged
-
-`FieldSection` — the per-field row (label · control · hint) that every field draws for itself — did
-**not** move, and no field component changed. After the rename, fields land on exactly the same
-pixels; only the `<form>` element's own box changed, because the gutters that used to sit inside it
-now sit outside it.
-
-## Installing
-
-`FormRenderer` still depends on `FormBuilder`, never the reverse — `add FormRenderer` pulls both.
-
-The registry moved to match. `FormBuilder` **dropped** `FormStepper` and `HeaderBar`, so
-`add FormBuilder` on its own now installs a smaller tree: the fields, and no chrome. `FormRenderer`
-**gained** those two plus `SectionBlock` and `Button`.
-
-Note that `FormBuilder` **keeps** its `SectionBlock` dependency even though `FormRenderer.Section`
-moved away — `FormBuilder.Table` renders a `SectionBlock variant="Table"` shell of its own, so a
-standalone `add FormBuilder` still gets a working table field.

package/docs/reference/cli.md

@@ -1,112 +0,0 @@
----
-title: CLI Reference
-description: The torch-glare CLI — copy components, hooks, utils, layouts, and providers into your project.
-group: reference
-keywords: [cli, torch-glare, init, add, copy-in, glare.json]
----
-
-# CLI Reference
-
-TORCH Glare is a **copy-in** component library: the `torch-glare` CLI copies source files
-directly into your project (like shadcn/ui). You own the copied code and import it from your
-own local path — you never import components from the npm package.
-
-Run any command with `npx` (no global install required):
-
-```bash
-npx torch-glare@latest <command> [name]
-```
-
-Run a command **without** a name to pick from an interactive list.
-
-## Commands
-
-| Command | Description |
-| --- | --- |
-| `init` | Create `glare.json`, install the Tailwind packages, **and wire your stylesheet**. Run once per project. |
-| `add [Component]` | Copy a component **and its dependencies** into your project. |
-| `hook [hook]` | Copy a hook (usually pulled in automatically as a dependency). |
-| `util [util]` | Copy a utility (e.g. `cn`, usually pulled in automatically). |
-| `layout [layout]` | Copy a layout. |
-| `provider [provider]` | Copy a provider (e.g. `ThemeProvider`). |
-| `update` | Re-sync everything already installed with the latest templates. |
-
-Component names are **case-sensitive PascalCase** — `add DatePicker`, not `add datepicker`.
-Every command takes a **bare name** — `hook useDragDrop`, not `hook useDragDrop.tsx` — and every one
-accepts `-f, --force`.
-
-## `init`
-
-```bash
-npx torch-glare@latest init
-```
-
-Three things, in order:
-
-1. Creates `glare.json`.
-2. Installs the Tailwind packages the design system needs, using your detected package manager.
-3. **Wires your entry stylesheet** — `app/globals.css`, `src/app/globals.css`, `src/index.css`,
-   `styles/globals.css` — with the `@import`/`@plugin` block. Re-running is safe: if the block is
-   already there it says so and changes nothing.
-
-On Tailwind v3 the plugins belong in `tailwind.config.*` instead. `init` prints the snippet rather
-than editing that file, since its shape is yours.
-
-> Without step 3 the project builds cleanly and renders every component **unstyled** — the design
-> tokens simply resolve to nothing. If that happens, check that `@import "tailwindcss"` is the
-> first line: CSS requires imports to precede other at-rules, so an import placed after a `@plugin`
-> is silently dropped.
-
-`glare.json` controls where files are copied:
-
-```json
-{
-  "path": "@/"
-}
-```
-
-Files are copied into `<path>/components`, `<path>/hooks`, `<path>/utils`,
-`<path>/layouts`, and `<path>/providers`. Import them from that path.
-
-## `add`
-
-```bash
-npx torch-glare@latest add Button
-```
-
-Copies `Button` **plus its full dependency closure** — nested components, hooks, and utils —
-and installs any required npm packages (e.g. `@radix-ui/*`) using your project's package
-manager. After adding, import from your local alias:
-
-```tsx
-import { Button } from "@/components/Button";
-
-export function Example() {
-  return <Button variant="PrimeStyle">Click me</Button>;
-}
-```
-
-It ends with a summary — `✅ DataViews → ./: 56 installed (56 items).` — so a partial install is
-visible rather than something you discover at build time.
-
-Dependencies come from the generated `registry.json`, resolved in one pass, so each item is copied
-exactly once however many things import it.
-
-Existing files are never overwritten. Use `--force` to re-copy — it applies to **the whole
-dependency closure**, not just the component you named — or `update` to re-sync everything.
-
-## `update`
-
-```bash
-npx torch-glare@latest update
-```
-
-Re-copies every installed component, hook, util, layout, and provider from the latest
-templates. Review the diff afterward, since it overwrites your local copies.
-
-## See also
-
-- [Theme reference](./theme.md)
-- [Components reference](./components.md)
-- [Hooks reference](./hooks.md)
-- [Providers reference](./providers.md)