@jielga/tmdatagrid 2.0.0-beta.9 → 2.0.1

package/skills/grouping/SKILL.md

@@ -14,12 +14,12 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.9'
+  library_version: '2.0.1'
 sources:
-  - 'Jielga/TMDataGrid:src/docs/grouping.md'
-  - 'Jielga/TMDataGrid:src/docs/summary-row.md'
-  - 'Jielga/TMDataGrid:src/tmdatagrid/core/grouping.ts'
-  - 'Jielga/TMDataGrid:src/tmdatagrid/core/summary.ts'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/grouping.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/summary-row.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/core/grouping.ts'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/core/summary.ts'
 ---
 
 # TMDataGrid - Grouping and totals
@@ -86,9 +86,12 @@ would pass a row that looks real but is the wrong one. Group rows therefore:
 - do not fire `onRowClick` or the cell handlers
 - cannot be highlighted, pinned, or given a details panel
 - never edit
+- are still handed to `rowStyle` and `rowClassName`, with that child's record
+  as `original`, so guard a callback reading `original` with
+  `row.getIsGrouped()` and colour the group rows with `--dg-row-group-bg`
 - carry `data-grouped="true"` and `data-depth`, with `--dg-row-group-bg`
-  behind them. `data-grouped` is on every row, `"true"` or `"false"`, so match
-  the value rather than the bare attribute
+  behind them. `data-grouped` is present only on group rows, so
+  `[data-grouped]` and `[data-grouped="true"]` are equivalent
 
 A group row's checkbox selects every record under it at any depth, including
 records inside collapsed sub-groups, showing a tick once all are selected and a
@@ -142,7 +145,9 @@ aggregateColumn({ table, columnId: "location", fn: "uniqueCount" });
 ```
 
 It follows the filters deliberately. A total that does not change as the user
-narrows the grid is misleading.
+narrows the grid is misleading. Its only argument is `table`, so a toolbar
+readout or any other component holding the table reads the same total without a
+`footer`.
 
 Pinned columns keep their lanes in the summary row, the generated lanes define
 no `footer` so their cells stay blank, and the row is sticky at
@@ -168,7 +173,7 @@ Correct:
 columnHelper.accessor("salary", { header: "Salary", aggregationFn: "sum" });
 ```
 
-Source: `src/docs/grouping.md` (Aggregation).
+Source: `packages/tmdatagrid/docs/grouping.md` (Aggregation).
 
 ### HIGH Looking for the grouped column in the grid
 
@@ -183,7 +188,7 @@ Correct, when the column must stay:
 useTMDataGrid({ data, columns, groupedColumnMode: "reorder" });
 ```
 
-Source: `src/docs/grouping.md` (What grouping does to the grid).
+Source: `packages/tmdatagrid/docs/grouping.md` (What grouping does to the grid).
 
 ### HIGH Combining the pager with grouping
 
@@ -192,14 +197,16 @@ out instead of paging the tree, so a footer count wired to `getPageCount()`
 reports a number nobody can navigate to. Read
 `isPagingActive(table, features)` before trusting the pager state.
 
-Source: `src/docs/grouping.md` (Grouping suspends pagination).
+Source: `packages/tmdatagrid/docs/grouping.md` (Grouping suspends pagination).
 
 ### HIGH Handing a group row to a row callback
 
 Group rows do not fire `onRowClick` or the cell handlers, and cannot be pinned,
 expanded or edited. Their `row.original` is an arbitrary child's record, so a
 bulk action built from `row.original` on the tree lane acts on one record
-instead of the group.
+instead of the group. `rowStyle` and `rowClassName` are the callbacks group
+rows do reach, so one reading `row.original` colours the group by whichever
+child came first.
 
 Correct:
 
@@ -207,9 +214,17 @@ Correct:
 import { getGroupDataRows } from "@jielga/tmdatagrid";
 
 const records = getGroupDataRows(groupRow).map((row) => row.original);
+
+<TMDataGrid.Table<Employee>
+  rowStyle={(row) =>
+    !row.getIsGrouped() && row.original.status === "Terminated"
+      ? { "--row-bg": "color-mix(in srgb, var(--mantine-color-red-6) 12%, transparent)" }
+      : undefined
+  }
+/>;
 ```
 
-Source: `src/docs/grouping.md` (Group rows are not data rows).
+Source: `packages/tmdatagrid/docs/grouping.md` (Group rows are not data rows).
 
 ### MEDIUM Totalling the page instead of the data
 
@@ -217,7 +232,7 @@ Source: `src/docs/grouping.md` (Group rows are not data rows).
 `table.getRowModel().rows` instead totals only what is currently paged in, and
 under virtualization not even that: only the mounted rows.
 
-Source: `src/docs/summary-row.md` (Totalling a column).
+Source: `packages/tmdatagrid/docs/summary-row.md` (Totalling a column).
 
 ### MEDIUM Grouping a server-paged grid
 
@@ -237,7 +252,7 @@ useTMDataGrid({
 });
 ```
 
-Source: `src/docs/grouping.md` (Server-side grids).
+Source: `packages/tmdatagrid/docs/grouping.md` (Server-side grids).
 
 ## Reference
 
@@ -258,7 +273,7 @@ Source: `src/docs/grouping.md` (Server-side grids).
 | `isPagingActive` | Export | `(table, features) => boolean` | – | Whether the pager is slicing anything. `false` while grouped. |
 | `--dg-row-group-bg` | CSS variable | colour | Themed | Group row background. |
 | `--dg-summary-height` | CSS variable | length | From `size` | Height of the summary row. |
-| `data-grouped` · `data-depth` | Data attributes | – | – | `"true"` on group rows (published on every row), and the nesting level on every row. |
+| `data-grouped` · `data-depth` | Data attributes | – | – | `"true"` on group rows (absent on the rest), and the nesting level on every row. |
 
 See also: the `rows` skill for selection and the details lane, and the `data`
 skill for the pager grouping suspends.

package/skills/migrating-to-2/SKILL.md

@@ -0,0 +1,244 @@
+---
+name: migrating-to-2
+description: >
+  Upgrade code written against a 2.0.0-beta release of TMDataGrid to 2.0.0, as a
+  checklist to run over a codebase. Covers the edit.commitAll / saveDrafts /
+  addRows result objects and the silent `if (await saveDrafts())` trap, the
+  onSaveDrafts return type renamed to TMDataGridSaveDraftsResponse, every
+  removed name with its replacement (submitAll, onCommitDrafts, rows / added,
+  pendingCount, cellExport, exportGridToCsv, the cell-matrix functions,
+  toExcelCsv, downloadTextFile, labels.exportCsv), the helpers no longer
+  exported, removing row annotations and casts from meta.options and
+  meta.edit.enabled callbacks, and the behaviour changes. Load when upgrading
+  @jielga/tmdatagrid from a 2.0 beta, or when an import or a property from the
+  beta no longer resolves.
+metadata:
+  type: lifecycle
+  library: '@jielga/tmdatagrid'
+  library_version: '2.0.1'
+sources:
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/migrating-to-2.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/index.ts'
+---
+
+# TMDataGrid - Migrating from the 2.0 beta to 2.0.0
+
+2.0.0 removes every name deprecated during the 2.0 beta, stops exporting a set
+of internal helpers, and changes what three edit calls resolve. Run the steps
+below in order over the codebase. Step 1 finds code that still compiles but
+behaves differently; the compiler finds most of the rest.
+
+## 1. CRITICAL Read `ok` from commitAll and saveDrafts
+
+`edit.commitAll()` and `edit.saveDrafts()` resolve an object instead of a
+`boolean`. A truthiness check on the old `boolean` still compiles and is now
+always true, so a failed save reports success with no error.
+
+Search for: `commitAll(` and `saveDrafts(`, including the `actions.save` and
+`actions.commitAll` of a `TMDataGrid.DraftActions` `renderActions` slot, which
+resolve the same objects.
+
+| Call | Resolves |
+| --- | --- |
+| `edit.commitAll()` · `actions.commitAll()` | `TMDataGridCommitAllResult`: `{ ok, committed, open }` |
+| `edit.saveDrafts()` · `actions.save()` | `TMDataGridSaveDraftsResult`: `{ ok, saved, kept, reopened }` |
+| `edit.addRows(rows, options)` | `TMDataGridAddRowsResult`: `{ ok, committed, open }` - `ok` is new |
+| `edit.commit(rowId)` | `boolean`, unchanged |
+
+Wrong (compiles, always true):
+
+```tsx
+if (await grid.edit.saveDrafts()) notify("Saved");
+const done = await grid.edit.commitAll();
+if (!done) return;
+```
+
+Correct:
+
+```tsx
+const { ok, kept, reopened } = await grid.edit.saveDrafts();
+if (ok) notify("Saved");
+else notify(`${kept.length + reopened.length} rows need attention`);
+
+const { ok: committed } = await grid.edit.commitAll();
+if (!committed) return;
+```
+
+Each list holds row ids, and temp ids for new rows. `ok` is `true` when `open`
+is empty, or, for `saveDrafts()`, when `kept` and `reopened` are both empty.
+Also check every other use of the result: `.then((saved) => ...)`, a `return`
+of it from a `boolean` function, `!result`, `result ? ... : ...` and
+`Boolean(result)`.
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Read the batch edit results).
+
+## 2. Rename the onSaveDrafts return type
+
+The type of what `editing.onSaveDrafts` may return is renamed
+`TMDataGridSaveDraftsResponse`. `TMDataGridSaveDraftsResult` is now the type
+`edit.saveDrafts()` resolves, so code that kept the old name for the callback
+fails to compile.
+
+Search for: `TMDataGridSaveDraftsResult`. Where it types an `onSaveDrafts`
+callback or its return value, replace it:
+
+```tsx
+// beta
+import type { TMDataGridSaveDraftsResult } from "@jielga/tmdatagrid";
+
+// 2.0.0
+import type { TMDataGridSaveDraftsResponse } from "@jielga/tmdatagrid";
+```
+
+Where it types the value of `await edit.saveDrafts()`, keep it.
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Rename the onSaveDrafts return type).
+
+## 3. Replace removed names
+
+Search for each name in the first column and replace it:
+
+| Removed | Use instead |
+| --- | --- |
+| `edit.submitAll()` | `edit.commitAll()`, then `edit.saveDrafts()` |
+| `editing.onCommitDrafts` | `editing.onSaveDrafts` |
+| `rows` and `added` in the `onSaveDrafts` payload | `updated` and `created` |
+| `TMDataGridEditCommitDraftsArgs` | `TMDataGridSaveDraftsArgs` |
+| `state.pendingCount` in a `TMDataGrid.DraftActions` slot | `state.draftCount` or `state.openCount` |
+| `cellExport` on `TMDataGrid.Table` | `exportOptions` on `useTMDataGrid` |
+| `exportGridToCsv` | `exportGrid` |
+| `TMDataGridCellExportOptions`, `DEFAULT_CELL_EXPORT_OPTIONS`, `fromCellExportOptions` | `TMDataGridExportOptions`, `DEFAULT_EXPORT_OPTIONS` |
+| `buildCellMatrix`, `buildGridCellMatrix`, `BuildCellMatrixArgs`, `TMDataGridCellMatrix` | `buildExportData`, `BuildExportDataArgs`, `TMDataGridExportData` |
+| `toExcelCsv` | `csvExcelFormat` |
+| `downloadTextFile` | `downloadFile` |
+| `labels.exportCsv` | `labels.exportCells` |
+
+Search for `onSaveDrafts` as well, and check what each callback reads off its
+payload.
+
+### submitAll
+
+`submitAll()` was `commitAll()` followed by `saveDrafts()`. Call both, and
+combine the results where one answer is needed:
+
+```tsx
+const committed = await grid.edit.commitAll();
+const saved = await grid.edit.saveDrafts();
+const ok = committed.ok && saved.ok;
+```
+
+### The CSV export options
+
+`separator` and `decimalComma` move into a format; `includeHeaders` and
+`fileName` stay in the options. `exportOptions` on the hook applies to every
+export the grid offers, the cell-range menu included.
+
+```tsx
+// beta
+<TMDataGrid.Table cellExport={{ separator: ",", decimalComma: false, fileName: "orders" }} />;
+exportGridToCsv({ table, options: { separator: ",", decimalComma: false } });
+
+// 2.0.0
+const exportOptions = {
+  format: csvExcelFormat({ separator: ",", decimalComma: false }),
+  fileName: "orders",
+} satisfies TMDataGridExportOptions;
+
+const grid = useTMDataGrid({ data, columns, exportOptions });
+await exportGrid({ table: grid.table, options: exportOptions });
+```
+
+### The matrix functions
+
+The export functions now return values, not text. A format writes the text:
+
+```tsx
+// beta
+const csv = toExcelCsv(buildGridCellMatrix({ table }), { separator: ";" });
+downloadTextFile({ fileName: "export.csv", text: csv });
+
+// 2.0.0
+const data = buildExportData({ table });
+const csv = await csvExcelFormat().write(data, { includeHeaders: true });
+downloadFile({ fileName: "export.csv", content: csv, mimeType: "text/csv;charset=utf-8" });
+```
+
+For a cell range, pass `rows` and `bounds` to `buildExportData` instead of
+`rows`, `columns` and `bounds` to `buildCellMatrix`. `toClipboardText(data)`
+writes the tab-separated text for the clipboard.
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Replace removed names).
+
+## 4. Remove annotations and casts from meta callbacks
+
+The `row` that `meta.options` and `meta.edit.enabled` callbacks receive is
+typed with the row type of `createTMDataGridColumnHelper<TData>()`:
+`Row<TMDataGridFeatures, TData>`. A callback whose parameter is annotated with
+the untyped row no longer compiles.
+
+Search for: `options:` and `enabled:` inside column `meta`, and
+`Row<TMDataGridFeatures, TMDataGridRowData>` or `as ` casts on `row.original`
+next to them. Remove the annotation and the cast:
+
+```tsx
+// beta
+meta: {
+  edit: {
+    enabled: (row: Row<TMDataGridFeatures, TMDataGridRowData>) =>
+      (row.original as Employee).status !== "Terminated",
+  },
+}
+
+// 2.0.0
+meta: {
+  edit: { enabled: (row) => row.original.status !== "Terminated" },
+}
+```
+
+Columns built without the helper keep the untyped row,
+`Row<TMDataGridFeatures, TMDataGridRowData>`; leave those as they are.
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Remove annotations from meta callbacks).
+
+## 5. Replace helpers that are no longer exported
+
+These names are internal to the grid and are no longer exported from
+`@jielga/tmdatagrid`. An import of one fails to compile. Search the imports
+from `@jielga/tmdatagrid` for each:
+
+| Removed | Use instead |
+| --- | --- |
+| `getDefaultOperator` | `getColumnDefaultOperator(column)` |
+| `isColumnEditableForRow` | `edit.canEditCell(row, column)` |
+| `isColumnReorderable` | `getColumnCapabilities(column, features).canReorder` |
+| `measureColumnContentWidth` | `autosizeColumn` |
+| `tmDataGridFeatures` | The `TMDataGridFeatures` type |
+| `isSameCell`, `resolveCellMove`, `ResolveCellMoveArgs`, `TMDataGridCellCoords`, `TMDataGridCellNav` | No public replacement; internal to the grid. |
+| `boundsCellCount`, `boundsEdges`, `isWithinBounds` | No public replacement; internal to the grid. |
+| `getColumnFilterControl` | No public replacement; internal to the grid. |
+| `TMDataGridColumnLayout` | No public replacement; internal to the grid. |
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Replace un-exported helpers).
+
+## 6. Check the behaviour changes
+
+- Under `editing.draft` without `onSaveDrafts`, a deletion whose
+  `onRowDelete` throws keeps its deletion mark and is reported in `kept`. In
+  the beta, `saveDrafts()` rejected and the mark was lost. Search for a
+  `try` / `catch` around `saveDrafts()` that expected the rejection, and read
+  `kept` instead.
+- The Swedish labels `TMDATAGRID_LABELS_SV` say "Välj" for selecting: "Välj
+  alla", "Välj alla rader", "Välj rad" and "Välj grupp". Update tests that find
+  these controls by their Swedish name.
+
+Source: `packages/tmdatagrid/docs/migrating-to-2.md` (Behaviour changes).
+
+## 7. Verify
+
+Run the project's typecheck: an import of a removed or un-exported name, and a
+meta callback annotated with the untyped row, fail there. Then run the tests
+that save or commit edits, since the truthiness check of step 1 and the
+behaviour changes of step 6 compile.
+
+See also: the `editing` skill for the result objects and the draft store, and
+the `data` skill for the export API.

package/skills/options/SKILL.md

@@ -14,11 +14,12 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.9'
+  library_version: '2.0.1'
 sources:
-  - 'Jielga/TMDataGrid:src/docs/use-tm-data-grid.md'
-  - 'Jielga/TMDataGrid:src/tmdatagrid/useTMDataGrid.tsx'
-  - 'Jielga/TMDataGrid:src/tmdatagrid/core/persistence.ts'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/use-tm-data-grid.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/persistence.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/useTMDataGrid.tsx'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/core/persistence.ts'
 ---
 
 # TMDataGrid - useTMDataGrid
@@ -30,6 +31,8 @@ const grid = useTMDataGrid<TData>(options);
 // { table, ui, edit, features, labels, resetSettings, scrollToRow }
 ```
 
+The signature is
+`useTMDataGrid<TData>(options: UseTMDataGridOptions<TData>): TMDataGridApi<TData>`.
 Spread the result onto `TMDataGrid`.
 
 ## Options
@@ -74,7 +77,7 @@ rather than forwarded to TanStack.
 | Slice | Default |
 | --- | --- |
 | `pagination` | `{ pageIndex: 0, pageSize: 25 }` - inert until pagination is enabled |
-| `columnPinning.left` | The checkbox column, followed by any columns you provide |
+| `columnPinning.start` | The checkbox column, followed by any columns you provide |
 | `globalFilterFn` | `"includesString"` |
 
 ### Controlled state
@@ -124,9 +127,9 @@ changes. Separate keys let one group be cleared without touching the other.
 
 | Field | Type | Default | Description |
 | --- | --- | --- | --- |
-| `dataKey` | `string \| [string, DataSlice[]]` | – | Storage key for the data group. |
-| `settingsKey` | `string \| [string, SettingsSlice[]]` | – | Storage key for the settings group. |
-| `storageMode` | `"localStorage" \| "sessionStorage"` | `"localStorage"` | Storage area. |
+| `dataKey` | `TMDataGridPersistKey<TMDataGridDataSlice>`: `string \| [string, DataSlice[]]` | – | Storage key for the data group. |
+| `settingsKey` | `TMDataGridPersistKey<TMDataGridSettingsSlice>`: `string \| [string, SettingsSlice[]]` | – | Storage key for the settings group. |
+| `storageMode` | `TMDataGridStorageMode`: `"localStorage" \| "sessionStorage"` | `"localStorage"` | Storage area. `"sessionStorage"` is per tab. |
 | `serialize` | `(value) => string` | `JSON.stringify` | Serializes before storing. |
 | `deserialize` | `(value: string) => unknown` | `JSON.parse` | Parses a stored payload. |
 
@@ -168,7 +171,8 @@ survives the data changing under it the way the column layout does. `expanded` i
 a data slice for the opposite reason.
 
 `DATA_STATE_SLICES` and `SETTINGS_STATE_SLICES` export the same values. Slice
-names are typed per group, so only valid names are accepted.
+names are typed per group, `TMDataGridDataSlice` and `TMDataGridSettingsSlice`,
+so only valid names are accepted.
 
 Restoring happens once on mount through `initialState`. Writing is a subscription
 to the table store, so state changed directly through the table API is persisted
@@ -176,12 +180,20 @@ too. Only selected slices are read back, and unrecognised keys are ignored. All
 storage access is guarded - if storage is unavailable, disabled or full,
 persistence is skipped rather than throwing.
 
+A payload from another version is dropped whole, not migrated. Payloads carry
+the exported `PERSIST_PAYLOAD_VERSION`; anything else, including everything
+written by a 0.x build, is discarded. Restored state is realigned against the
+columns that exist: entries naming a column removed between deploys are
+dropped.
+
+Source: `packages/tmdatagrid/docs/persistence.md` (Behaviour).
+
 ## Return value
 
 | Field | Type | Description |
 | --- | --- | --- |
 | `table` | `Table<TMDataGridFeatures, TData>` | The TanStack table instance. |
-| `ui` | `Store<TMDataGridUiState, TMDataGridUiActions>` | State of the filter and column panels. |
+| `ui` | `TMDataGridUiStore`: `Store<TMDataGridUiState, TMDataGridUiActions>` | State of the filter and column panels. |
 | `edit` | `TMDataGridEditApi` | The edit engine, inert until `editing` is set. See the `editing` skill. |
 | `features` | `TMDataGridFeatureFlags` | Table-level feature switches, re-read on each render. |
 | `labels` | `TMDataGridLabels` | The resolved label set, overrides merged over English. |
@@ -208,8 +220,8 @@ const filterPanelOpen = useSelector(grid.ui, (state) => state.filterPanelOpen);
 | --- | --- |
 | `openFilterPanel` | `(columnId?: string \| null) => void` |
 | `closeFilterPanel` | `() => void` |
-| `setColumnsPanelOpen` | `(open: boolean) => void` |
-| `toggleColumnsPanel` | `() => void` |
+| `focusPanelFilter` | `(columnId: string \| null) => void` |
+| `focusHeaderFilter` | `(columnId: string \| null) => void` |
 | `startColumnDrag` | `(columnId: string) => void` |
 | `endColumnDrag` | `() => void` |
 | `setHighlightedRow` | `(rowId: string \| null) => void` |

package/skills/rows/SKILL.md

@@ -17,14 +17,15 @@ description: >
 metadata:
   type: core
   library: '@jielga/tmdatagrid'
-  library_version: '2.0.0-beta.9'
+  library_version: '2.0.1'
 sources:
-  - 'Jielga/TMDataGrid:src/docs/row-selection.md'
-  - 'Jielga/TMDataGrid:src/docs/row-interaction.md'
-  - 'Jielga/TMDataGrid:src/docs/row-styling.md'
-  - 'Jielga/TMDataGrid:src/docs/row-details.md'
-  - 'Jielga/TMDataGrid:src/docs/row-pinning.md'
-  - 'Jielga/TMDataGrid:src/tmdatagrid/core/rowSelection.ts'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/row-selection.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/row-interaction.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/column-menu.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/row-styling.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/row-details.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/docs/row-pinning.md'
+  - 'Jielga/TMDataGrid:packages/tmdatagrid/src/core/rowSelection.ts'
 ---
 
 # TMDataGrid - Rows
@@ -187,13 +188,15 @@ array rather than a node:
 
 Returning an empty list leaves the column with no menu button at all.
 
+Source: `packages/tmdatagrid/docs/column-menu.md`.
+
 ## Row styling
 
 ```tsx
 <TMDataGrid.Table<Employee>
   striped
   rowStyle={(row) =>
-    row.original.status === "Terminated"
+    !row.getIsGrouped() && row.original.status === "Terminated"
       ? { "--row-bg": "color-mix(in srgb, var(--mantine-color-red-6) 12%, transparent)" }
       : undefined
   }
@@ -211,8 +214,9 @@ are not striped.
 Rows carry `data-selected`, `data-selected-bg`, `data-highlighted`,
 `data-grouped`, `data-depth`, `data-context-menu` and `data-row-id`, so a
 stylesheet can target any of it without a callback. The boolean attributes are
-published on every row as `"true"` or `"false"`, so match the value
-(`[data-grouped="true"]`), not the bare attribute. Pick a `--row-bg` that
+present, with the value `"true"`, only while they apply - `data-grouped` only
+on group rows - so `[data-grouped]` and `[data-grouped="true"]` are
+equivalent. Pick a `--row-bg` that
 reads under both colour schemes - a `-0` Mantine shade is near-white and
 unreadable in dark mode; mix a mid shade into transparency instead.
 
@@ -295,7 +299,7 @@ Correct:
 rowStyle={() => ({ "--row-bg": "pink" })}
 ```
 
-Source: `src/docs/row-styling.md` (Set `--row-bg`, not `background`).
+Source: `packages/tmdatagrid/docs/row-styling.md` (Set `--row-bg`, not `background`).
 
 ### CRITICAL Reading the selection without subscribing
 
@@ -317,7 +321,7 @@ const selected = useSelector(grid.table.store, () =>
 );
 ```
 
-Source: `src/docs/row-selection.md` (Acting on a selection).
+Source: `packages/tmdatagrid/docs/row-selection.md` (Acting on a selection).
 
 ### HIGH Looking for the highlight in `rowSelection`
 
@@ -338,7 +342,7 @@ Correct:
 const current = useSelector(grid.ui, (state) => state.highlightedRowId);
 ```
 
-Source: `src/docs/row-selection.md` (The highlight is not a selection).
+Source: `packages/tmdatagrid/docs/row-selection.md` (The highlight is not a selection).
 
 ### HIGH Expecting a click handler to replace the built-in behaviour
 
@@ -353,7 +357,7 @@ Correct, when the click should only navigate:
 useTMDataGrid({ data, columns, selectionMode: "highlight" });
 ```
 
-Source: `src/docs/row-interaction.md`.
+Source: `packages/tmdatagrid/docs/row-interaction.md`.
 
 ### HIGH Reading `row.getIsExpanded()` in a cell without subscribing
 
@@ -366,7 +370,7 @@ Correct:
 const expanded = useSelector(row.table.store, () => row.getIsExpanded());
 ```
 
-Source: `src/docs/row-details.md` (Opening a row from elsewhere).
+Source: `packages/tmdatagrid/docs/row-details.md` (Opening a row from elsewhere).
 
 ### MEDIUM Assuming group rows behave like data rows
 
@@ -375,7 +379,7 @@ Group rows are built on their first child's record. They do not fire
 never pin, they take no row number, and they have no details panel. A handler
 written as though every row reaches it silently skips them.
 
-Source: `src/docs/row-interaction.md`, `src/docs/row-pinning.md`.
+Source: `packages/tmdatagrid/docs/row-interaction.md`, `packages/tmdatagrid/docs/row-pinning.md`.
 
 ### MEDIUM Open panels closing when `data` is replaced
 
@@ -388,7 +392,7 @@ Correct:
 useTMDataGrid({ data, columns, renderDetails, autoResetExpanded: false });
 ```
 
-Source: `src/docs/row-details.md`.
+Source: `packages/tmdatagrid/docs/row-details.md`.
 
 ### MEDIUM Expecting pinned rows to persist
 
@@ -396,7 +400,7 @@ Source: `src/docs/row-details.md`.
 layout store outlives any one data set. A pinned id whose row leaves `data` is
 not shown, and returns to its edge if the data comes back.
 
-Source: `src/docs/row-pinning.md`.
+Source: `packages/tmdatagrid/docs/row-pinning.md`.
 
 ## References
 

package/skills/rows/references/rows-api.md

@@ -6,7 +6,7 @@ Reference for the `rows` skill.
 
 | Name | Kind | Type | Default | What it does |
 | --- | --- | --- | --- | --- |
-| `selectionMode` | Option | `"checkbox" \| "row" \| "checkboxAndHighlight" \| "highlight"` | `"checkbox"` | What selecting looks like and what a row click does. |
+| `selectionMode` | Option | `TMDataGridSelectionMode`: `"checkbox" \| "row" \| "checkboxAndHighlight" \| "highlight"` | `"checkbox"` | What selecting looks like and what a row click does. |
 | `enableRowSelection` | Table option | `boolean \| ((row) => boolean)` | `true` | `false` removes the checkbox column and row-click selection. |
 | `enableMultiRowSelection` | Table option | `boolean` | `true` | `false` limits the selection to one row and drops group checkboxes. |
 | `showSelectedBackground` | Option | `boolean` | Follows the mode | Whether selected rows take a background tint. |
@@ -14,7 +14,8 @@ Reference for the `rows` skill.
 | `onHighlightedRowChange` | Callback | `(rowId: string \| null) => void` | – | Fires when the highlight moves. |
 | `SELECT_COLUMN_ID` | Export | `"__select__"` | – | Id of the generated checkbox column. |
 | `getSelectableRowIds` | Export | `(table) => string[]` | – | Ids the header checkbox would select. |
-| `resolveRowSelectionClick` | Export | `(args) => ResolvedRowSelection` | – | The desktop-list click rules, for a custom surface. |
+| `resolveRowSelectionClick` | Export | `(args: ResolveRowSelectionClickArgs) => ResolvedRowSelection` | – | The desktop-list click rules, for a custom surface. |
+| `ResolveRowSelectionClickArgs` · `TMDataGridRowClickModifiers` | Types | `{ rows, rowId, anchorRowId, modifiers, selection }` · `{ toggle, extend }` | – | What `resolveRowSelectionClick` takes, and its `modifiers`. |
 | `getDisplayedRows` | Export | `(table) => Row[]` | – | The rows currently on screen, paging respected. |
 | `isPagingActive` | Export | `(table) => boolean` | – | Whether a pager is in play. |
 
@@ -31,11 +32,13 @@ All are props of `TMDataGrid.Table`, not hook options.
 | `onCellClick` | `(args) => void` | Cell click. `args` is `TMDataGridCellEventArgs`. |
 | `onCellDoubleClick` | `(args) => void` | Cell double-click. |
 | `onCellContextMenu` | `(args) => void` | Cell right-click. |
-| `renderRowContextMenu` | `({ table, row, cell, close, internalItems }) => ReactNode` | Contents of the row's context menu. `null` for no menu. Reading `internalItems` hands the composition over. |
-| `renderColumnMenuItems` | `({ column, table, internalItems }) => ReactNode[]` | Contents of a column's menu. An empty list removes the button. |
+| `renderRowContextMenu` | `TMDataGridRowContextMenuRenderer`: `(args: TMDataGridRowContextMenuArgs) => ReactNode` | Contents of the row's context menu. `null` for no menu. Reading `internalItems` hands the composition over. |
+| `renderColumnMenuItems` | `TMDataGridColumnMenuItemsRenderer`: `(args: TMDataGridColumnMenuItemsArgs) => ReactNode[]` | Contents of a column's menu. An empty list removes the button. |
 | `rowContextMenuProps` | `MenuProps` | Passed to the Mantine `Menu` unchanged, apart from its open state. |
 
-`TMDataGridCellEventArgs` is `{ cell, row, column, event }`. The context-menu
+`TMDataGridCellEventArgs` is `{ cell, row, column, event }`.
+`TMDataGridRowContextMenuArgs` is `{ table, row, cell, close, internalItems }`,
+and `TMDataGridColumnMenuItemsArgs` is `{ column, table, internalItems }`. The context-menu
 slot's `cell` is `null` only when a custom cell renderer stopped the
 event. One `Menu` serves the whole body rather than one per row: a closed
 Mantine `Popover` still runs its hooks on every render, and the virtualized body
@@ -76,13 +79,14 @@ Row data attributes:
 
 | Name | Kind | Type | Default | What it does |
 | --- | --- | --- | --- | --- |
-| `renderDetails` | Option | `({ row, table }) => ReactNode` | – | Contents of the panel. Setting it adds the lane. |
+| `renderDetails` | Option | `TMDataGridDetailsRenderer`: `(args: TMDataGridDetailsArgs) => ReactNode` | – | Contents of the panel. Setting it adds the lane. `TMDataGridDetailsArgs` is `{ row, table }`. |
 | `renderDetailsEstHeight` | Option | `number` | `160` | Height the virtualizer assumes for an unmeasured panel. |
 | `initialState.expanded` | Table option | `ExpandedState` | `{}` | Rows open at mount. A `data` slice, so it persists. |
 | `autoResetExpanded` | Table option | `boolean` | `true` | `false` keeps panels open when `data` changes. |
 | `DETAILS_COLUMN_ID` | Export | `"__details__"` | – | Id of the generated chevron column. |
 | `resolveExpandAll` | Export | `(args) => ExpandedState` | – | Expand or collapse every group, or every panel, but not both. |
 | `areAllRowsExpanded` | Export | `(args) => boolean` | – | Whether every row of one target is open. |
+| `TMDataGridExpandAllArgs` · `TMDataGridExpandTarget` | Types | `{ rows, expanded, target }` · `"groups" \| "details"` | – | What `areAllRowsExpanded` takes (`resolveExpandAll` also takes `expand`), and its `target`. |
 | `data-dg-part="details"` | Data attribute | – | – | The panel element, carrying the row's `data-row-id`. |
 
 One `expanded` state opens two unrelated things - a group row into its children,