`). No effect in store mode (its header is unconditional). |\n| `showFooter` | `boolean` | `true` | Shows/hides the Cancel/Submit button row, both modes. |\n| `showBack` | `boolean` | `true` | Shows the back-arrow icon button. See the asymmetric per-mode behavior under `onBack`. |\n| `showCard` | `boolean` | `true` | **Only honored in store mode** (wraps output in `Card` vs. a plain `
`). In fields mode, Card-vs-div is decided solely by `showHeader && (title \\|\\| description \\|\\| showBack)` ā this prop is read but never checked there. |\n| `listPath` | `string` | - | Fallback destination for `handleBack()` when no `onBack` is given, in both modes. |\n| `icon` | `component` | - | **Only rendered in store mode when `showCard` is `false`.** Not used in the Card-wrapped store header, and not used anywhere in fields mode. |\n| `className` | `string` | - | Applied to the outer `Card`/`div` wrapper, both modes. |\n| `getBreadcrumbName` | `function(values)` | - | Store mode only, active only while editing (`uuid` route param present). Called with `store.form.values` once they look populated; its return value is registered via `useBreadcrumb().setBreadcrumbName(uuid, name)` and cleared on unmount. Requires an ancestor `BreadcrumbProvider`. |\n| `loading` | `boolean` | `false` | OR'd with the store's own `loading` (store mode). Disables fields and combines with `submitting` to disable Submit. |\n| `submitting` | `boolean` | `false` | OR'd with the store's own `form.isSubmitting` (store mode). Disables Cancel/Submit and swaps Submit's label/icon for a spinner + \"Saving...\". |\n\n> **Not implemented / dead props:** there is no `onSuccess` callback ā store mode's success message is a hardcoded toast (`\"{title} created/updated successfully\"`); the closest customization hook is `onAfterCreate` (create only). `backLabel` is destructured but never rendered anywhere ā it has no effect.\n\n**Edit-mode detection**: create-vs-edit is determined solely by `Boolean(useParams().uuid)` ā `CrudForm` must be rendered on a route with a literal `:uuid` param (not `:id`, and not an `id` prop). This flag drives the title prefix, whether `fetchById`/`fetchAndPopulateForm`/`fetchOne` runs, and whether submit calls `store.update(uuid, values)` vs `store.create(values)`. Fields mode ignores this entirely ā there, \"edit\" is just whatever `initialData` you pass in.\n\n### Usage\n\n**Store mode** (requires a hand-written store matching the shape described in the warning above), rendered on routes like `/users/new` and `/users/:uuid/edit`:\n\n```jsx\nimport { CrudForm, QInput } from '@bomjan133/react-crud-ui';\n\nfunction UserForm() {\n return (\n values.name}\n onBeforeSubmit={(values) => ({ ...values, email: values.email.trim().toLowerCase() })}\n onAfterCreate={(result, navigate) => navigate(`/users/${result.uuid}/edit`)}\n >\n s.form.values.name) ?? ''}\n onChange={(val) => useUserFormStore.getState().setFormValue('name', val)}\n />\n s.form.values.email) ?? ''}\n onChange={(val) => useUserFormStore.getState().setFormValue('email', val)}\n />\n \n );\n}\n```\n\n**Fields mode** (self-contained `react-hook-form`, no store, no router param required ā pass `initialData` for edit, omit it for create):\n\n```jsx\nimport { CrudForm } from '@bomjan133/react-crud-ui';\n\n {\n await api.saveUser(data);\n toast.success('Saved');\n }}\n onCancel={() => navigate('/users')}\n onBack={() => navigate('/users')}\n/>\n```\n\n---\n\n## CrudDetail\n\nA detail-view component for a single record. It supports two distinct rendering modes, and can source its data either from a Zustand-style store hook (`useStore`) or directly via a `data` prop.\n\n**Mode selection is automatic and based on `children`:**\n- **Store + render-prop mode** ā used only when *both* `useStore` is passed **and** `children` is a function. Renders whatever `children(data)` returns inside a plain header + content wrapper (no Card).\n- **Fields-based mode** ā used in every other case (no `useStore`, or `useStore` without a function `children`, or `children` that isn't a function). Renders a `Card` with a field grid built from the `fields` array. **`children` is completely ignored in this mode.**\n\n`useStore` can also be used purely for fetching/deleting without triggering render-prop mode, as long as `children` isn't a function ā data then comes from the store and renders via `fields`.\n\n> ā ļø **`children` is a render-prop function, not a plain node**, and only takes effect when `us","readmeFilename":"README.md"}