@jielga/tmdatagrid 1.0.0 → 1.0.1

package/dist/index.d.ts

@@ -16,8 +16,8 @@ declare function TMDataGridColumnsPanel(): import("react").JSX.Element;
 /**
  * Batch mode's toolbar chrome: Save with the dirty-row count, and Discard.
  * Both read the edit store, so they grey out while nothing is dirty and the
- * Save spins while a submit is in flight. Works under any `editMode` — a
- * cellConfirm grid accumulating drafts can offer the same pair — and renders
+ * Save spins while a submit is in flight. Works under any `editMode` - a
+ * cellConfirm grid accumulating drafts can offer the same pair - and renders
  * nothing while editing is off.
  *
  * ```tsx
@@ -35,7 +35,7 @@ declare function TMDataGridEditActions(): import("react").JSX.Element | null;
  * The MUI-style filter surface: one row per active column filter, each row a
  * column / operator / value triple. It only ever reads and writes the table's
  * `columnFilters` state, so a `manualFiltering` grid gets the same panel for
- * free — the state is forwarded to the server instead of a row model.
+ * free - the state is forwarded to the server instead of a row model.
  */
 declare function TMDataGridFilterPanel(): import("react").JSX.Element | null;
 //#endregion
@@ -45,7 +45,7 @@ declare const DEFAULT_TMDATAGRID_SIZE: TMDataGridSize;
 /**
  * Row height per size, in px.
  *
- * The virtualizer needs this as a number — it cannot read the CSS variable —
+ * The virtualizer needs this as a number - it cannot read the CSS variable -
  * so the scale lives here and `TMDataGrid.module.css` mirrors it. `meta.rowHeight`
  * overrides it when a grid needs a height the scale doesn't offer.
  */
@@ -57,7 +57,7 @@ declare const SIZE_CONTROL_SIZE: Record<TMDataGridSize, MantineSize>;
 /**
  * Row shape the chrome components work against. They only ever touch columns,
  * rows and cells generically, so the concrete row type is erased at the context
- * boundary — the same trick Mantine uses for its compound components.
+ * boundary - the same trick Mantine uses for its compound components.
  */
 type TMDataGridRowData = Record<string, unknown>;
 type TMDataGridContextValue = TMDataGridApi<TMDataGridRowData> & {
@@ -73,7 +73,7 @@ declare function useTMDataGridContext(): TMDataGridContextValue;
  *
  * `-1` once cell selection is on, and this is what makes the promise of one tab
  * stop true. Without it the browser walks Tab into the checkbox of every
- * mounted row — a grid showing twenty rows would be twenty tab stops, and
+ * mounted row - a grid showing twenty rows would be twenty tab stops, and
  * scrolling would change how many. Enter or F2 steps into the cell instead,
  * which reaches a `-1` control perfectly well.
  *
@@ -119,14 +119,14 @@ type TMDataGridOptionsArgs = {
   fallback?: TMDataGridOptionsSource;
 };
 /**
- * Where a column's options come from — `meta.options`. One declaration feeds
+ * Where a column's options come from - `meta.options`. One declaration feeds
  * both the filter panel's value control and the cell editor.
  *
  * | Form | For |
  * | --- | --- |
  * | array | a known, fixed set |
  * | `"faceted"` | low-cardinality data columns: the distinct values present, via `getFacetedUniqueValues` |
- * | function | large or contextual sets — `row` is set when an editor asks, so options can depend on the record (city given country) |
+ * | function | large or contextual sets - `row` is set when an editor asks, so options can depend on the record (city given country) |
  */
 type TMDataGridOptionsSource = ReadonlyArray<TMDataGridOption | string> | "faceted" | ((args: TMDataGridOptionsArgs) => ReadonlyArray<TMDataGridOption | string>);
 /**
@@ -160,12 +160,12 @@ declare function optionsToComboboxData(options: ReadonlyArray<TMDataGridOption>)
  *
  * TanStack resolves `filterFn` statically per column, so the operator travels
  * inside the filter *value* instead. That keeps the whole filter model plain,
- * serialisable JSON — which is what makes it portable to a server-side
+ * serialisable JSON - which is what makes it portable to a server-side
  * `manualFiltering` table (just forward `columnFilters` to the API).
  *
  * `value` is a string array under `isAnyOf` / `isNoneOf` (the set the cell is
  * tested against), a `[min, max]` pair under `between` (an empty string means
- * that end is open), and a single string everywhere else — dates travel as
+ * that end is open), and a single string everywhere else - dates travel as
  * ISO `YYYY-MM-DD` strings, booleans as `"true"` / `"false"`. Still plain
  * JSON.
  */
@@ -179,11 +179,11 @@ declare const FILTER_OPERATOR_LABELS: Record<TMDataGridFilterOperator, string>;
 declare function getOperatorsForType(type: TMDataGridColumnType): readonly TMDataGridFilterOperator[];
 declare function getDefaultOperator(type: TMDataGridColumnType): TMDataGridFilterOperator;
 declare function operatorNeedsValue(operator: TMDataGridFilterOperator): boolean;
-/** Whether the operator's value is a string array — `isAnyOf` / `isNoneOf`. */
+/** Whether the operator's value is a string array - `isAnyOf` / `isNoneOf`. */
 declare function operatorTakesArrayValue(operator: TMDataGridFilterOperator): boolean;
-/** Whether the operator's value is a `[min, max]` pair — `between`. */
+/** Whether the operator's value is a `[min, max]` pair - `between`. */
 declare function operatorTakesRangeValue(operator: TMDataGridFilterOperator): boolean;
-/** The untouched value a fresh filter starts with — the operator's shape, empty. */
+/** The untouched value a fresh filter starts with - the operator's shape, empty. */
 declare function emptyValueForOperator(operator: TMDataGridFilterOperator): string | ReadonlyArray<string>;
 /**
  * A filter only narrows the row set once it has something to compare against.
@@ -194,15 +194,15 @@ declare function isFilterActive(value: unknown): boolean;
 /**
  * One-line description of a single filter, as shown on a filter pill.
  *
- * The type's default operator is left implicit — "First name: Sofia" reads the
- * way a person would say it — while any other operator is spelled out, since
+ * The type's default operator is left implicit - "First name: Sofia" reads the
+ * way a person would say it - while any other operator is spelled out, since
  * that is the part a reader cannot guess.
  */
 declare function formatFilterLabel({ label, type, filter, operatorLabels }: {
   label: string;
   type: TMDataGridColumnType;
   filter: TMDataGridFilterValue;
-  /** Localized operator names — `labels.operators`. Defaults to English. */
+  /** Localized operator names - `labels.operators`. Defaults to English. */
   operatorLabels?: Record<TMDataGridFilterOperator, string>;
 }): string;
 /**
@@ -214,33 +214,33 @@ declare function tmDataGridFilterFn<TFeatures extends TableFeatures, TData exten
 //#endregion
 //#region .types-tmp/core/editEngine.d.ts
 /**
- * How commits happen — one axis, each mode a thin policy over the same
+ * How commits happen - one axis, each mode a thin policy over the same
  * engine. See `editMode` on `UseTMDataGridOptions`.
  */
 type TMDataGridEditMode = "cell" | "cellConfirm" | "row" | "batch";
 /**
  * One editing row's live form. TanStack Form's `FormApi`, not a wrapper: the
- * engine is a form library, and everything mid-edit — values, dirty state,
- * errors, async validation, submit lifecycle — is form state, read off
+ * engine is a form library, and everything mid-edit - values, dirty state,
+ * errors, async validation, submit lifecycle - is form state, read off
  * `form.store` with the same selector idiom as the rest of the grid.
  *
  * The alias erases Form's validator generics the way `TMDataGridRowData`
  * erases the row type: the concrete types lived at the `useTMDataGrid` call.
  */
 type TMDataGridRowEditForm = AnyFormApi;
-/** The live field a cell editor binds to — TanStack Form's own `FieldApi`. */
+/** The live field a cell editor binds to - TanStack Form's own `FieldApi`. */
 type TMDataGridEditField = AnyFieldApi;
 /**
  * A validator as TanStack Form takes it: a Standard Schema (Zod, Valibot,
  * ArkType…) or a plain function returning an error or nothing. Forwarded
- * untouched — the vocabulary is Form's, not a grid re-implementation.
+ * untouched - the vocabulary is Form's, not a grid re-implementation.
  */
 type TMDataGridValidator = StandardSchemaV1<unknown, unknown> | ((args: {
   value: never;
   fieldApi: never;
 }) => unknown);
 /**
- * `meta.validate` — per-column field validators. A bare schema or function is
+ * `meta.validate` - per-column field validators. A bare schema or function is
  * shorthand for `{ onChange: it }`; the object form takes every trigger
  * TanStack Form defines, `Async` variants and debounce included.
  */
@@ -255,7 +255,7 @@ type TMDataGridFieldValidate = TMDataGridValidator | {
   onSubmitAsync?: TMDataGridValidator;
 };
 /**
- * `rowValidators` — form-level validators for the whole row, where
+ * `rowValidators` - form-level validators for the whole row, where
  * cross-field rules live. Passed into each row form's `validators` untouched;
  * pathed issues land on the matching fields, pathless ones on the row.
  */
@@ -274,29 +274,29 @@ type TMDataGridRowValidators = {
 type TMDataGridEditChange = {
   /** Column the field maps back to, for consumers thinking in columns. */
   columnId: string;
-  /** The data path — `getEditFieldName` of the column. */
+  /** The data path - `getEditFieldName` of the column. */
   field: string;
   previous: unknown;
   next: unknown;
 };
 type TMDataGridEditCommitArgs<TData extends RowData> = {
   rowId: string;
-  /** The whole row as edited — for the consumer who saves records. */
+  /** The whole row as edited - for the consumer who saves records. */
   value: TData;
   /** The row as it was when editing began. */
   original: TData;
-  /** Per-field diff — for the consumer who PATCHes. One entry in cell mode. */
+  /** Per-field diff - for the consumer who PATCHes. One entry in cell mode. */
   changes: Array<TMDataGridEditChange>;
   /** Which policy committed. */
   source: TMDataGridEditMode;
 };
-/** What one open row's form looks like from outside — the cell markers. */
+/** What one open row's form looks like from outside - the cell markers. */
 type TMDataGridEditRowProjection = {
   /** Field names whose value differs from the original. */
   dirtyFields: ReadonlyArray<string>;
   /** Field names carrying a validation error. */
   errorFields: ReadonlyArray<string>;
-  /** A row-level error — a pathless `.refine()`, or a rejected commit. */
+  /** A row-level error - a pathless `.refine()`, or a rejected commit. */
   hasRowError: boolean;
   isSubmitting: boolean;
 };
@@ -304,7 +304,7 @@ type TMDataGridEditRowProjection = {
  * The grid-facing index of everything mid-edit. A projection synced from the
  * open forms' stores, so body cells subscribe to this one store for their
  * dirty/error markers instead of one store per form. Only the editor host
- * reads a form's store directly — it is mounted for one cell at a time.
+ * reads a form's store directly - it is mounted for one cell at a time.
  */
 type TMDataGridEditState = {
   /** The cell whose editor is open; `columnId: null` is a whole row (row mode). */
@@ -315,24 +315,24 @@ type TMDataGridEditState = {
   /** Rows with a live form. In cell mode at most one; in batch, many. */
   openRowIds: ReadonlyArray<string>;
   rows: Record<string, TMDataGridEditRowProjection>;
-  /** Phase 4 — rows being created, not yet in `data`. */
+  /** Phase 4 - rows being created, not yet in `data`. */
   newRows: ReadonlyArray<{
     tempId: string;
   }>;
-  /** Phase 4 — rows marked deleted under batch mode. */
+  /** Phase 4 - rows marked deleted under batch mode. */
   deletedRowIds: ReadonlyArray<string>;
 };
 type ErasedRow = Row<TMDataGridFeatures, TMDataGridRowData>;
 type ErasedColumn = Column<TMDataGridFeatures, TMDataGridRowData, unknown>;
 /**
- * What a cell editor is handed — deliberately both vocabularies at once. The
+ * What a cell editor is handed - deliberately both vocabularies at once. The
  * form side is TanStack Form's real `field` API (`field.state.value`,
  * `field.state.meta.errors`, `field.handleChange`, `field.handleBlur`), so a
  * custom calendar, slider or async combobox binds to it exactly as it would
  * inside any TanStack Form. The table side is where the editor is standing.
  *
  * The built-ins are implemented against this same contract, so
- * `meta.editor` is not a special case — it is the slot the defaults
+ * `meta.editor` is not a special case - it is the slot the defaults
  * fill, and the exported built-ins can be wrapped instead of replaced.
  */
 type TMDataGridEditorArgs = {
@@ -344,9 +344,9 @@ type TMDataGridEditorArgs = {
   row: ErasedRow;
   column: ErasedColumn;
   table: TMDataGridTable<TMDataGridRowData>;
-  /** What Enter would do — commit the edit. For the editor's own UI. */
+  /** What Enter would do - commit the edit. For the editor's own UI. */
   commit: () => Promise<boolean>;
-  /** What Escape would do — drop the draft. */
+  /** What Escape would do - drop the draft. */
   cancel: () => void;
   size: TMDataGridSize;
   /**
@@ -355,29 +355,29 @@ type TMDataGridEditorArgs = {
    */
   autoFocus: boolean;
   /**
-   * Set when typing opened the editor (the Sheets gesture) — the built-ins
+   * Set when typing opened the editor (the Sheets gesture) - the built-ins
    * replace the value with it and keep typing. A custom editor may ignore it.
    */
   seedText?: string;
 };
 /**
- * `meta.editor` — replaces the built-in editor for this column. Rendered as
+ * `meta.editor` - replaces the built-in editor for this column. Rendered as
  * JSX, never invoked as a bare function, so hooks are legal inside. Define it
  * at module scope: a new identity per render remounts the editor mid-edit.
  */
 type TMDataGridEditorComponent = ComponentType<TMDataGridEditorArgs>;
-/** A new row being committed — `onRowAdd`, and `submitAll`'s `added`. */
+/** A new row being committed - `onRowAdd`, and `submitAll`'s `added`. */
 type TMDataGridRowAddArgs<TData extends RowData> = {
   /** The engine's placeholder id; the real id is the consumer's to mint. */
   tempId: string;
   value: TData;
 };
-/** A deletion — `onRowDelete`. */
+/** A deletion - `onRowDelete`. */
 type TMDataGridRowDeleteArgs<TData extends RowData> = {
   rowId: string;
   row: Row<TMDataGridFeatures, TData>;
 };
-/** What `submitAll` hands `onEditCommitBatch` — everything pending at once. */
+/** What `submitAll` hands `onEditCommitBatch` - everything pending at once. */
 type TMDataGridEditCommitBatchArgs<TData extends RowData> = {
   /** Every valid dirty existing row. */
   rows: Array<TMDataGridEditCommitArgs<TData>>;
@@ -393,7 +393,7 @@ type TMDataGridEditCommitBatchArgs<TData extends RowData> = {
  * nested rows work for free: `accessorKey: "address.city"` edits
  * `values.address.city`. A column built on `accessorFn` has no path and is
  * not editable unless `meta.editField` names one. TanStack's default column
- * id turns dots into underscores — which is why this starts from
+ * id turns dots into underscores - which is why this starts from
  * `accessorKey`, never from `id`.
  */
 declare function getEditFieldName(column: {
@@ -403,17 +403,17 @@ declare function getEditFieldName(column: {
     };
   };
 }): string | null;
-/** What Delete writes into a cell — the type's honest empty value. */
+/** What Delete writes into a cell - the type's honest empty value. */
 declare function clearedValueForType(type: TMDataGridColumnType): unknown;
 /**
- * The engine plus its store — `api.edit`.
+ * The engine plus its store - `api.edit`.
  *
  * "One row, one form": `getForm` hands out the same `FormApi` the inline
  * editors write through, so a consumer can render it in a drawer or a detail
  * panel and share values, dirty state and errors with the cells.
  */
 type TMDataGridEditApi = {
-  /** The projection store — subscribe with `useSelector(edit.store, …)`. */
+  /** The projection store - subscribe with `useSelector(edit.store, …)`. */
   store: Store<TMDataGridEditState>;
   /** Current snapshot, for reads outside React. */
   readonly state: TMDataGridEditState;
@@ -424,7 +424,7 @@ type TMDataGridEditApi = {
    * switched it off, and the row takes edits at all.
    */
   canEditCell: (row: ErasedRow, column: ErasedColumn) => boolean;
-  /** Whether the row takes edits at all — the edit lane's pencil gate. */
+  /** Whether the row takes edits at all - the edit lane's pencil gate. */
   canEditRow: (row: ErasedRow) => boolean;
   /** Opens an editor. `columnId: null` opens the whole row (row mode). */
   begin: (target: {
@@ -432,7 +432,7 @@ type TMDataGridEditApi = {
     columnId: string | null;
   }) => void;
   /**
-   * Commits one row — `form.handleSubmit` under the hood. Resolves `true`
+   * Commits one row - `form.handleSubmit` under the hood. Resolves `true`
    * when the form is gone: validation passed and `onEditCommit` resolved, or
    * there was nothing to save. `false` keeps the form open with its errors.
    */
@@ -440,42 +440,42 @@ type TMDataGridEditApi = {
   /** Drops one row's draft. */
   cancel: (rowId: string) => void;
   /**
-   * Closes the editor without touching the draft — what blur does under
+   * Closes the editor without touching the draft - what blur does under
    * `"cellConfirm"`, where the dirty cell keeps waiting for its ✓.
    */
   deactivate: () => void;
   /** Drops every draft. */
   cancelAll: () => void;
-  /** Commits every open row — batch mode's save. `true` when all landed. */
+  /** Commits every open row - batch mode's save. `true` when all landed. */
   submitAll: () => Promise<boolean>;
-  /** Writes the type's empty value into a cell and commits it — Delete. */
+  /** Writes the type's empty value into a cell and commits it - Delete. */
   clearCell: (rowId: string, columnId: string) => Promise<boolean>;
   /**
    * Opens a new entry row (the sticky block under the header) seeded from
-   * `newRowDefaults`. Returns its temporary id — a form with no backing row
+   * `newRowDefaults`. Returns its temporary id - a form with no backing row
    * yet. Committing it calls `onRowAdd` (immediate modes) or joins
    * `submitAll`'s `added` (batch).
    */
   addRow: () => string;
   /**
    * Deletes a row: `onRowDelete` straight away under the immediate modes;
-   * under batch it toggles the id in `deletedRowIds` — the row renders
+   * under batch it toggles the id in `deletedRowIds` - the row renders
    * struck through until `submitAll` reports it. On an uncommitted entry
    * row it just discards the entry.
    */
   deleteRow: (rowId: string) => void;
-  /** Whether delete chrome makes sense — the lane's trash gate. */
+  /** Whether delete chrome makes sense - the lane's trash gate. */
   canDeleteRows: () => boolean;
 };
 /**
  * `meta.validate` normalised to the object TanStack Form's `validators`
- * option takes — a bare schema or function is shorthand for `{ onChange }`.
+ * option takes - a bare schema or function is shorthand for `{ onChange }`.
  */
 declare function normalizeFieldValidate(validate: TMDataGridFieldValidate | undefined): Record<string, unknown> | undefined;
 //#endregion
 //#region .types-tmp/core/labels.d.ts
 /**
- * Every user-facing string in the grid — menu items, panels, tooltips, the
+ * Every user-facing string in the grid - menu items, panels, tooltips, the
  * pager, and the `aria-label`s a screen reader speaks. One flat object, so an
  * override is a spread rather than a deep merge; `operators` is the single
  * nested record and {@link mergeLabels} folds it separately.
@@ -486,9 +486,9 @@ declare function normalizeFieldValidate(validate: TMDataGridFieldValidate | unde
 type TMDataGridLabels = {
   /** Filter operator names, as shown in the operator dropdown and on pills. */
   operators: Record<TMDataGridFilterOperator, string>;
-  /** "Manage columns" — the burger button and the header menu item. */
+  /** "Manage columns" - the burger button and the header menu item. */
   manageColumns: string;
-  /** "Filters" — the funnel button and the filter panel's title. */
+  /** "Filters" - the funnel button and the filter panel's title. */
   filters: string;
   searchPlaceholder: string;
   searchLabel: string;
@@ -502,7 +502,7 @@ type TMDataGridLabels = {
   /** Menu/panel name of the generated row-number gutter. */
   rowNumberColumnLabel: string;
   /**
-   * The truly-empty message — no data and no filters. Filtered-empty says
+   * The truly-empty message - no data and no filters. Filtered-empty says
    * {@link noResults} instead; only one of the two is the user's own doing.
    */
   noRows: string;
@@ -516,7 +516,7 @@ type TMDataGridLabels = {
   filterTo: string;
   /** `DgTriStateFilter`'s no-filter segment. */
   filterAll: string;
-  /** What a boolean column's `true` reads as — its filter choice and cell text. */
+  /** What a boolean column's `true` reads as - its filter choice and cell text. */
   booleanTrue: string;
   booleanFalse: string;
   addFilter: string;
@@ -574,9 +574,9 @@ type TMDataGridLabels = {
   saveAllEdits: (rows: number) => string;
   /** `EditActions`' Discard. */
   discardAllEdits: string;
-  /** The entry row's ✓ — commit the add. */
+  /** The entry row's ✓ - commit the add. */
   confirmNewRow: string;
-  /** The entry row's ✕ — drop the entry. */
+  /** The entry row's ✕ - drop the entry. */
   discardNewRow: string;
   /** The lane's trash can. */
   deleteRow: string;
@@ -602,7 +602,7 @@ type TMDataGridLabels = {
 };
 /**
  * What the `labels` option accepts: any subset, merged over the English
- * defaults — so `{ noResults: "Inga rader" }` is a complete configuration.
+ * defaults - so `{ noResults: "Inga rader" }` is a complete configuration.
  */
 type TMDataGridLabelsOverride = Partial<Omit<TMDataGridLabels, "operators">> & {
   operators?: Partial<Record<TMDataGridFilterOperator, string>>;
@@ -614,13 +614,13 @@ declare function mergeLabels(override?: TMDataGridLabelsOverride): TMDataGridLab
 //#endregion
 //#region .types-tmp/core/filterControls.d.ts
 /**
- * What a filter control is handed — the value slot of one filter-panel row.
+ * What a filter control is handed - the value slot of one filter-panel row.
  *
  * The contract is value-only: the control reads `operator` to shape itself
  * (a `between` pair renders two ends, an `equals` a single input) and calls
  * `onChange` with the bare value; the grid composes the operator-aware
  * `TMDataGridFilterValue` around it. A control never builds that wrapper and
- * never writes the operator — `table` is the escape hatch for the rare
+ * never writes the operator - `table` is the escape hatch for the rare
  * control that must.
  */
 type TMDataGridFilterControlArgs = {
@@ -628,13 +628,13 @@ type TMDataGridFilterControlArgs = {
   table: TMDataGridTable<TMDataGridRowData>;
   /** The row's currently selected operator. Read-only for the control. */
   operator: TMDataGridFilterOperator;
-  /** The bare filter value — never the `{ operator, value }` wrapper. */
+  /** The bare filter value - never the `{ operator, value }` wrapper. */
   value: string | ReadonlyArray<string>;
   /** Writes the bare value; the grid pairs it with the current operator. */
   onChange: (next: string | ReadonlyArray<string>) => void;
   /**
    * The column's options through `resolveColumnOptions`, pre-resolved for a
-   * column that declares `meta.options` or is select-shaped. Empty otherwise —
+   * column that declares `meta.options` or is select-shaped. Empty otherwise -
    * a control wanting faceted values on other columns resolves them itself.
    */
   options: ReadonlyArray<TMDataGridOption>;
@@ -642,14 +642,14 @@ type TMDataGridFilterControlArgs = {
   labels: TMDataGridLabels;
 };
 /**
- * `meta.filterControl` — replaces the built-in value control for this column.
+ * `meta.filterControl` - replaces the built-in value control for this column.
  * Rendered as JSX, never invoked as a bare function, so hooks are legal
  * inside. Define it at module scope so its identity is stable across renders.
  */
 type TMDataGridFilterControlComponent = ComponentType<TMDataGridFilterControlArgs>;
 //#endregion
 //#region .types-tmp/core/quickSearch.d.ts
-/** How the quick search matches — see `quickSearchMode` on the hook options. */
+/** How the quick search matches - see `quickSearchMode` on the hook options. */
 type TMDataGridQuickSearchMode = "fuzzy" | "contains";
 /** What {@link fuzzyGlobalFilterFn} records per column via `addMeta`. */
 type FuzzyFilterMeta = {
@@ -657,8 +657,8 @@ type FuzzyFilterMeta = {
 };
 /**
  * Match-sorter ranking as the global filter: a row passes when a globally
- * filterable column ranks above match-sorter's threshold — typos and skipped
- * characters forgiven — and the rank is recorded for the ordering to read.
+ * filterable column ranks above match-sorter's threshold - typos and skipped
+ * characters forgiven - and the rank is recorded for the ordering to read.
  *
  * TanStack stops probing a row's columns at the first passing one, so the
  * recorded ranks cover the columns up to and including it; the best of those
@@ -699,8 +699,8 @@ type TMDataGridSettingsSlice = (typeof SETTINGS_STATE_SLICES)[number];
 /**
  * A storage key, optionally narrowed to a subset of its group's slices.
  *
- * - `"employees.data"` — persists every slice in the group.
- * - `["employees.data", ["sorting"]]` — persists only the listed slices.
+ * - `"employees.data"` - persists every slice in the group.
+ * - `["employees.data", ["sorting"]]` - persists only the listed slices.
  */
 type TMDataGridPersistKey<TSlice extends string> = string | readonly [key: string, slices: readonly TSlice[]];
 /** Same values as Mantine's `StorageType`, which the package does not re-export. */
@@ -722,7 +722,7 @@ type TMDataGridPersistence = {
  * collide with. A payload whose version does not match is dropped whole: a
  * migration would be guessing at a shape this code no longer knows, and the
  * cost of dropping is one lost layout. Payloads written before versioning
- * existed (≤0.4.0) have no stamp and are dropped the same way — the 1.0
+ * existed (≤0.4.0) have no stamp and are dropped the same way - the 1.0
  * wave's one-time break, named in its changeset.
  */
 declare const PERSIST_PAYLOAD_VERSION = 1;
@@ -741,10 +741,10 @@ declare const PERSIST_PAYLOAD_VERSION = 1;
  * what applies the per-column overrides.
  */
 /**
- * How rows are selected — see `selectionMode` on {@link UseTMDataGridOptions}.
+ * How rows are selected - see `selectionMode` on {@link UseTMDataGridOptions}.
  *
- * One axis, because the two things a config could set independently — which
- * chrome selects, and what a bare row click does — cannot both be free: a click
+ * One axis, because the two things a config could set independently - which
+ * chrome selects, and what a bare row click does - cannot both be free: a click
  * can either toggle a multi-selection or move the highlight, never both. Folding
  * them into one value makes that conflict unrepresentable rather than something
  * to warn about.
@@ -756,10 +756,10 @@ type TMDataGridSelectionMode =
 "row" |
 /** Checkbox column multi-selects, and a row click highlights one row. */
 "checkboxAndHighlight" |
-/** No selection at all — a row click only highlights. Master-detail. */
+/** No selection at all - a row click only highlights. Master-detail. */
 "highlight";
 /**
- * How cells are selected — see `cellSelection` on {@link UseTMDataGridOptions}.
+ * How cells are selected - see `cellSelection` on {@link UseTMDataGridOptions}.
  *
  * A mode rather than a pair of booleans, for the reason
  * {@link TMDataGridSelectionMode} is one: "cells can be selected" and "more
@@ -776,7 +776,7 @@ type TMDataGridCellSelectionMode =
 type TMDataGridFeatureFlags = {
   sorting: boolean;
   filtering: boolean;
-  /** Whether the quick search may filter — `enableGlobalFilter`. */
+  /** Whether the quick search may filter - `enableGlobalFilter`. */
   globalFiltering: boolean;
   hiding: boolean;
   pinning: boolean;
@@ -791,7 +791,7 @@ type TMDataGridFeatureFlags = {
   /** Whether a bare row click toggles the selection. Only under `"row"`. */
   rowClickSelects: boolean;
   /**
-   * Whether more than one row can be selected at once — TanStack's
+   * Whether more than one row can be selected at once - TanStack's
    * `enableMultiRowSelection`. Off, the grid drops the select-all header
    * checkbox: TanStack's `toggleAllRowsSelected` only consults `getCanSelect`,
    * so that control would select every row and walk straight past the limit.
@@ -802,14 +802,14 @@ type TMDataGridFeatureFlags = {
   /** Whether a selected row takes the highlight colour. Follows the mode. */
   showSelectedBackground: boolean;
   /**
-   * The single highlighted row — clicking a row highlights it, for a detail
+   * The single highlighted row - clicking a row highlights it, for a detail
    * panel to follow. State of its own, not a slice of `rowSelection`, which is
    * what lets it coexist with a checkbox multi-selection.
    */
   highlightRow: boolean;
   /**
    * Whether cells can be selected at all. Off unless `cellSelection` asks for
-   * it — it takes the body's tab stop off the row and puts it on a cell, and
+   * it - it takes the body's tab stop off the row and puts it on a cell, and
    * reports the grid to assistive technology as a `grid` rather than a `table`,
    * which is a different promise about what the keyboard does.
    */
@@ -827,7 +827,7 @@ type TMDataGridFeatureFlags = {
   /**
    * Row grouping: the "Group by" items in the header menu and the generated
    * tree column. On unless `enableGrouping: false`, since an ungrouped grid
-   * looks and behaves exactly as it did before — `grouping` starts empty, and
+   * looks and behaves exactly as it did before - `grouping` starts empty, and
    * an empty grouping state passes straight through the row model.
    *
    * The exception is `manualPagination`, where the client holds one page rather
@@ -836,14 +836,14 @@ type TMDataGridFeatureFlags = {
    * its own grouping can still say `enableGrouping: true` to override.
    */
   grouping: boolean;
-  /** Whether cells can be edited at all — `editMode` was set. */
+  /** Whether cells can be edited at all - `editMode` was set. */
   editing: boolean;
   /** The commit policy, or `null` while editing is off. */
   editMode: TMDataGridEditMode | null;
-  /** The generated row-number gutter — `enableRowNumbers`. Off by default. */
+  /** The generated row-number gutter - `enableRowNumbers`. Off by default. */
   rowNumbers: boolean;
   /**
-   * Whether rows can be pinned to the top or bottom edge — `enableRowPinning`,
+   * Whether rows can be pinned to the top or bottom edge - `enableRowPinning`,
    * boolean or per-row predicate. Off by default: pinning has no built-in
    * gesture, so a grid that never calls `row.pin()` has nothing to gain from
    * the body watching the state.
@@ -851,7 +851,7 @@ type TMDataGridFeatureFlags = {
   rowPinning: boolean;
   /**
    * Whether cells highlight the matched text while a contains-family filter
-   * or the quick search is active — `enableMatchHighlighting`. Off by
+   * or the quick search is active - `enableMatchHighlighting`. Off by
    * default, so a grid that has not asked pays nothing per cell.
    */
   matchHighlighting: boolean;
@@ -880,7 +880,7 @@ type TMDataGridColumnCapabilities = {
   canGroup: boolean;
 };
 declare function getColumnCapabilities(column: Column<TMDataGridFeatures, TMDataGridRowData, unknown>, features: TMDataGridFeatureFlags): TMDataGridColumnCapabilities;
-/** The same questions, asked of the whole grid — used to hide toolbar buttons. */
+/** The same questions, asked of the whole grid - used to hide toolbar buttons. */
 type TMDataGridCapabilities = {
   canSortAny: boolean;
   canFilterAny: boolean;
@@ -902,7 +902,7 @@ declare function getGridCapabilities(table: TMDataGridTable<TMDataGridRowData>,
  * Ids, because every other thing the grid does moves cells around: sorting
  * reorders rows, filtering removes them, dragging a header reorders columns. A
  * coordinate pair would silently come to mean a different cell after any of
- * them, while a pair of ids either still resolves or does not resolve at all —
+ * them, while a pair of ids either still resolves or does not resolve at all -
  * and "does not resolve" is a state the grid can handle honestly.
  *
  * Indices are what navigation is actually computed in, so they are resolved
@@ -920,7 +920,7 @@ type TMDataGridCellCoords = {
 type ResolveCellMoveArgs = {
   /** `KeyboardEvent.key`. */
   key: string;
-  /** Ctrl or Cmd — Home and End jump to the corner rather than the row end. */
+  /** Ctrl or Cmd - Home and End jump to the corner rather than the row end. */
   ctrlKey: boolean;
   from: TMDataGridCellCoords;
   rowCount: number;
@@ -937,7 +937,7 @@ type ResolveCellMoveArgs = {
  * Moves clamp at the edges instead of wrapping. Wrapping suits a menu, where
  * the items are a short ring; a grid is a coordinate space, and a Right at the
  * last column that lands on the first column of the next row loses the one
- * thing arrow keys are for — knowing where you will end up without looking.
+ * thing arrow keys are for - knowing where you will end up without looking.
  *
  * A clamped move returns the position it started from rather than `null`. The
  * caller still needs to know the key was handled: an arrow at the last row must
@@ -953,13 +953,13 @@ declare function isSameCell(a: TMDataGridCellPosition | null, b: TMDataGridCellP
  * A selected rectangle of cells, held as the two cells that span it.
  *
  * Two corners rather than a list of cells, because a range is a gesture, not a
- * set: dragging over 40 columns of a 100k-row grid would otherwise build — and
- * rebuild, on every mouse move — a list with millions of entries in it. Two
+ * set: dragging over 40 columns of a 100k-row grid would otherwise build - and
+ * rebuild, on every mouse move - a list with millions of entries in it. Two
  * positions describe the same thing and cost nothing to extend.
  *
  * `anchor` is where the gesture started and stays put; `focus` is the end that
  * moves. Which of the two is top-left depends on the direction it was dragged,
- * so nothing here assumes an order — see {@link resolveRangeBounds}.
+ * so nothing here assumes an order - see {@link resolveRangeBounds}.
  */
 type TMDataGridCellRange = {
   anchor: TMDataGridCellPosition;
@@ -983,7 +983,7 @@ type ResolveRangeBoundsArgs = {
  * corner no longer exists.
  *
  * A corner goes missing whenever a filter drops its row or a column is hidden,
- * and the honest answer then is that there is no rectangle — better than
+ * and the honest answer then is that there is no rectangle - better than
  * guessing at a replacement corner and quietly copying cells the user never
  * selected. The range itself is left alone: clearing it here would throw away
  * a selection that comes straight back when the filter is lifted.
@@ -1019,10 +1019,10 @@ type TMDataGridColumnMeta = {
    */
   type?: TMDataGridColumnType;
   /**
-   * The choices of a `select` / `multiSelect` column — one declaration feeding
+   * The choices of a `select` / `multiSelect` column - one declaration feeding
    * the filter panel's value control and the cell editor alike. A static
    * array, `"faceted"` (the distinct values present in the data), or a
-   * function of the table, column and — for editors — the row. See
+   * function of the table, column and, for editors, the row. See
    * {@link TMDataGridOptionsSource}.
    */
   options?: TMDataGridOptionsSource;
@@ -1031,7 +1031,7 @@ type TMDataGridColumnMeta = {
   align?: "left" | "right" | "center";
   /**
    * Size the column to its widest mounted content once, after the first rows
-   * render — unless a persisted or user-set width already covers it. The same
+   * render - unless a persisted or user-set width already covers it. The same
    * measurement as double-clicking the resize divider; see `autosizeColumn`.
    */
   autoSize?: boolean;
@@ -1043,13 +1043,13 @@ type TMDataGridColumnMeta = {
   enableOrdering?: boolean;
   /**
    * The operator a fresh filter on this column starts with, instead of the
-   * type's default — a salary column can open on `"between"`. Must be one of
+   * type's default - a salary column can open on `"between"`. Must be one of
    * the type's own operators.
    */
   defaultFilterOperator?: TMDataGridFilterOperator;
   /**
    * Replaces the built-in value control in this column's filter-panel row. A
-   * component rendered as JSX — hooks are legal inside — receiving the
+   * component rendered as JSX (hooks are legal inside), receiving the
    * value-only contract: it reads the current operator, writes the bare
    * value, and the grid composes the stored filter around it. Define it at
    * module scope. See {@link TMDataGridFilterControlArgs}.
@@ -1058,11 +1058,11 @@ type TMDataGridColumnMeta = {
   /**
    * Whether this column's cells take edits, once `editMode` is on. `false`
    * switches the column off outright; a predicate decides per row. Defaults
-   * to editable for any column that maps to a field — see {@link editField}.
+   * to editable for any column that maps to a field - see {@link editField}.
    */
   editable?: boolean | ((row: Row<TMDataGridFeatures, TMDataGridRowData>) => boolean);
   /**
-   * The data path this column edits, when it is not the `accessorKey` — the
+   * The data path this column edits, when it is not the `accessorKey` - the
    * only way a column built on `accessorFn` becomes editable. Dot paths reach
    * into nested records: `"address.city"`.
    */
@@ -1080,7 +1080,7 @@ type TMDataGridColumnMeta = {
   validate?: TMDataGridFieldValidate;
   /**
    * Replaces the built-in editor for this column. A component rendered as
-   * JSX — hooks are legal inside — receiving the live TanStack Form `field`
+   * JSX (hooks are legal inside), receiving the live TanStack Form `field`
    * API plus the table context, the same contract the built-ins fill. Define
    * it at module scope so its identity is stable across renders. See
    * {@link TMDataGridEditorArgs}.
@@ -1095,7 +1095,7 @@ type TMDataGridTableMeta = {
   rowHeight?: number;
   /**
    * Unfiltered row total. Only needed for server-driven grids, where the client
-   * never holds the full data set — `TMDataGrid.SummaryCount` uses it as denominator.
+   * never holds the full data set - `TMDataGrid.SummaryCount` uses it as denominator.
    */
   totalRowCount?: number;
 };
@@ -1296,13 +1296,13 @@ type TMDataGridUiState = {
    */
   draggedColumnId: string | null;
   /**
-   * The single highlighted row — the one a detail panel would be showing. Its
+   * The single highlighted row - the one a detail panel would be showing. Its
    * own concept, not a slice of `rowSelection`: under
    * `selectionMode: "checkboxAndHighlight"` the two coexist, and TanStack's one
    * selection map cannot hold both.
    *
    * Not pruned when the row is filtered out, paged away or dropped from `data`,
-   * matching how TanStack treats `rowSelection` — nothing there resets it
+   * matching how TanStack treats `rowSelection` - nothing there resets it
    * either. The row simply renders unhighlighted, and highlights again if it
    * comes back.
    */
@@ -1311,17 +1311,17 @@ type TMDataGridUiState = {
   selectionAnchorRowId: string | null;
   /**
    * The cell the keyboard is on, under `enableCellSelection`. `null` until the
-   * grid is first entered — and again whenever a consumer clears it.
+   * grid is first entered - and again whenever a consumer clears it.
    *
    * The state is the source of truth and DOM focus follows it, not the other
    * way around: under virtualization the cell it names is often not mounted,
    * which is exactly what a coordinate has to survive. Held as ids for the
-   * same reason — see {@link TMDataGridCellPosition}.
+   * same reason - see {@link TMDataGridCellPosition}.
    */
   focusedCell: TMDataGridCellPosition | null;
   /**
    * The selected rectangle, under `cellSelection: "range"`. Held as the two
-   * cells that span it — see {@link TMDataGridCellRange}.
+   * cells that span it - see {@link TMDataGridCellRange}.
    *
    * Always covers the focused cell: every gesture that moves the focus either
    * extends the rectangle or collapses it onto the new cell, so the two never
@@ -1337,21 +1337,21 @@ type TMDataGridUiActions = {
   startColumnDrag: (columnId: string) => void;
   endColumnDrag: () => void;
   /**
-   * Moves the active row, or clears it with `null` — which is how a consumer
+   * Moves the active row, or clears it with `null` - which is how a consumer
    * closing its detail panel puts the grid back in step.
    */
   setHighlightedRow: (rowId: string | null) => void;
   setSelectionAnchor: (rowId: string | null) => void;
   /**
    * Moves the focused cell, or clears it with `null`. DOM focus follows while
-   * the grid holds it — so this both moves the keyboard and, when the row is
+   * the grid holds it - so this both moves the keyboard and, when the row is
    * off screen, scrolls it into view. Called for every arrow key, and available
    * for a consumer putting the keyboard somewhere itself.
    */
   setFocusedCell: (cell: TMDataGridCellPosition | null) => void;
   /**
    * Sets the selected rectangle, or clears it with `null`. Does not move the
-   * focused cell — the two are set together by the gestures that change both,
+   * focused cell - the two are set together by the gestures that change both,
    * which is what keeps "extend the selection" and "move the cursor" separable.
    */
   setCellRange: (range: TMDataGridCellRange | null) => void;
@@ -1362,17 +1362,17 @@ type TMDataGridScrollAlign = "auto" | "start" | "center" | "end";
 type TMDataGridScrollToRowArgs = {
   /** The row's id, as `getRowId` produced it. */
   rowId: string;
-  /** Defaults to `"auto"` — the nearest edge, leaving a visible row alone. */
+  /** Defaults to `"auto"` - the nearest edge, leaving a visible row alone. */
   align?: TMDataGridScrollAlign;
 };
 /** @internal The body's scroll implementation. See `scrollToRow`. */
 type TMDataGridScroller = (args: TMDataGridScrollToRowArgs) => boolean;
-/** What `useTMDataGrid` returns — spread straight onto `<TMDataGrid />`. */
+/** What `useTMDataGrid` returns - spread straight onto `<TMDataGrid />`. */
 type TMDataGridApi<TData extends RowData> = {
   table: TMDataGridTable<TData>;
   ui: TMDataGridUiStore;
   /**
-   * The edit engine — open forms, dirty/error projections, and the verbs
+   * The edit engine - open forms, dirty/error projections, and the verbs
    * (`begin`, `commit`, `cancel`, `submitAll`). `edit.getForm(rowId)` hands
    * out the same TanStack Form the inline editors write through, so a drawer
    * or detail panel can share a row's draft. Inert until `editMode` is set.
@@ -1389,20 +1389,20 @@ type TMDataGridApi<TData extends RowData> = {
   /** Virtualizer overscan: the option, or {@link DEFAULT_OVERSCAN}. */
   overscan: number;
   /**
-   * Puts the settings state — visibility, order, widths, pinning, grouping —
+   * Puts the settings state - visibility, order, widths, pinning, grouping -
    * back to what a first visit with clean storage would have shown: the
    * consumer's `initialState` plus the structural lanes. With persistence
    * configured the reset writes through to storage like any other change.
    *
    * This, not TanStack's `resetColumnX()` family, is the reset for a
    * persisted grid: those reset to `initialState`, and the grid bakes the
-   * restored payload into `initialState` at mount — they would "reset" to
+   * restored payload into `initialState` at mount - they would "reset" to
    * the very layout being discarded.
    */
   resetSettings: () => void;
   /**
    * Scrolls a row into view. The grid is always virtualized, so a row far down
-   * the list has no element to scroll to — this moves the virtualizer instead,
+   * the list has no element to scroll to - this moves the virtualizer instead,
    * which is the only thing that can put one there.
    *
    * ```ts
@@ -1410,8 +1410,8 @@ type TMDataGridApi<TData extends RowData> = {
    * ```
    *
    * Answers whether the row could be reached. `false` means it is not in the
-   * current view at all — filtered out, on another page, or an id that matches
-   * no row — and nothing scrolled. A pinned row answers `true` without
+   * current view at all - filtered out, on another page, or an id that matches
+   * no row - and nothing scrolled. A pinned row answers `true` without
    * scrolling: it is already parked at an edge.
    *
    * Identity is stable, so it is safe in a dependency array.
@@ -1432,7 +1432,7 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
    */
   getRowId: NonNullable<TableOptions<TMDataGridFeatures, TData>["getRowId"]>;
   /**
-   * Form-level validators for the whole editing row — where cross-field
+   * Form-level validators for the whole editing row - where cross-field
    * rules live. TanStack Form's own vocabulary, Standard Schema included:
    *
    * ```tsx
@@ -1447,13 +1447,13 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
    * Pathed issues land on the matching columns; pathless ones on the row.
    */
   rowValidators?: TMDataGridRowValidators;
-  /** Rows the pencil skips — `false` keeps a row read-only in every mode. */
+  /** Rows the pencil skips - `false` keeps a row read-only in every mode. */
   isRowEditable?: (row: Row<TMDataGridFeatures, TData>) => boolean;
   /**
    * Called when an edit commits. The grid never mutates `data`: apply the
    * change and let the new data arrive back through `data` as always. The
-   * engine drops the draft only when this resolves — a slow save keeps the
-   * draft visible with a busy marker — and a rejection keeps the form open
+   * engine drops the draft only when this resolves - a slow save keeps the
+   * draft visible with a busy marker - and a rejection keeps the form open
    * with the error on the row.
    *
    * `changes` is the per-field diff (one entry in cell mode) for consumers
@@ -1461,7 +1461,7 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
    */
   onEditCommit?: (args: TMDataGridEditCommitArgs<TData>) => void | Promise<void>;
   /**
-   * Seed values for `edit.addRow()` — the entry row's starting point. A
+   * Seed values for `edit.addRow()` - the entry row's starting point. A
    * function is called per added row (fresh timestamps, empty arrays).
    */
   newRowDefaults?: TData | (() => TData);
@@ -1472,7 +1472,7 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
    */
   onRowAdd?: (args: TMDataGridRowAddArgs<TData>) => void | Promise<void>;
   /**
-   * Called by `edit.deleteRow` under the immediate modes — confirmation, if
+   * Called by `edit.deleteRow` under the immediate modes - confirmation, if
    * any, belongs in here. Under batch, deletions accumulate in
    * `edit.state.deletedRowIds` instead and are reported by `submitAll`.
    * Setting this also puts the trash can in the edit lane.
@@ -1483,7 +1483,7 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
  * The editing options travel together, and the type states it: without
  * `editMode` none of them has anything to act on, so passing one is a
  * compile error rather than a dead option; with it, `getRowId` becomes
- * required; and `onEditCommitBatch` exists only under `"batch"` — the one
+ * required; and `onEditCommitBatch` exists only under `"batch"` - the one
  * mode whose `submitAll` calls it.
  *
  * `editMode` itself turns cell editing on and picks how commits happen. Off
@@ -1491,7 +1491,7 @@ type TMDataGridEditingCallbacks<TData extends RowData> = {
  *
  * | Mode | Commit | Cancel |
  * | ---- | ------ | ------ |
- * | `"cell"` | Enter, Tab, blur — Sheets | Escape |
+ * | `"cell"` | Enter, Tab, blur - Sheets | Escape |
  * | `"cellConfirm"` | ✓ or Enter only; blur keeps the draft | ✕ or Escape |
  * | `"row"` | Save in the edit lane, or Ctrl+Enter | Cancel, or Escape |
  * | `"batch"` | `edit.submitAll()` | `edit.cancelAll()` |
@@ -1513,7 +1513,7 @@ type TMDataGridEditingOptions<TData extends RowData> = (TMDataGridEditingCallbac
   onEditCommitBatch?: (args: TMDataGridEditCommitBatchArgs<TData>) => void | Promise<void>;
 }) | (TMDataGridEditingCallbacks<TData> & {
   editMode: Exclude<TMDataGridEditMode, "batch">;
-  /** Only `"batch"`'s `submitAll` ever calls it — see the other branch. */
+  /** Only `"batch"`'s `submitAll` ever calls it - see the other branch. */
   onEditCommitBatch?: never;
 }) | {
   editMode?: never;
@@ -1528,14 +1528,14 @@ type TMDataGridEditingOptions<TData extends RowData> = (TMDataGridEditingCallbac
 type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridFeatures, TData>, "features"> & TMDataGridEditingOptions<TData> & {
   /**
    * Restore and persist table state across mounts. Two keys, because the two
-   * kinds of state have different lifetimes — see {@link TMDataGridPersistence}.
+   * kinds of state have different lifetimes - see {@link TMDataGridPersistence}.
    *
    * Keep the object referentially stable (module scope or `useMemo`); it is a
    * dependency of the subscription that writes back.
    */
   persist?: TMDataGridPersistence;
   /**
-   * Overrides for the grid's strings — menu items, panels, the pager, and
+   * Overrides for the grid's strings - menu items, panels, the pager, and
    * every `aria-label`. Any subset, merged over the English defaults; a full
    * Swedish dictionary ships as `TMDATAGRID_LABELS_SV`.
    *
@@ -1544,7 +1544,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * useTMDataGrid({ data, columns, labels: { noResults: "Inga rader" } });
    * ```
    *
-   * Keep the object referentially stable (module scope or `useMemo`) — the
+   * Keep the object referentially stable (module scope or `useMemo`) - the
    * chrome re-renders when its identity changes.
    */
   labels?: TMDataGridLabelsOverride;
@@ -1563,19 +1563,19 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * virtualization.
    *
    * The second grid-defined switch (TanStack defines no `enablePagination`
-   * option). `manualPagination: true` implies it — a server-paged grid needs
+   * option). `manualPagination: true` implies it - a server-paged grid needs
    * no extra flag.
    */
   enablePagination?: boolean;
   /**
    * The row-number gutter: a generated lane, outermost left, numbering the
-   * rows of the current view — sorted, filtered, continuing across pages,
+   * rows of the current view - sorted, filtered, continuing across pages,
    * with group rows unnumbered. Off by default.
    */
   enableRowNumbers?: boolean;
   /**
-   * How the quick search (`TMDataGrid.Search`) matches. `"fuzzy"` — the
-   * default — forgives typos and skipped characters, and while it is the
+   * How the quick search (`TMDataGrid.Search`) matches. `"fuzzy"` - the
+   * default - forgives typos and skipped characters, and while it is the
    * only thing narrowing the grid (no sort, no grouping) the rows order by
    * match quality, best first. `"contains"` is plain substring matching.
    * An explicit `globalFilterFn` overrides both.
@@ -1583,7 +1583,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
   quickSearchMode?: TMDataGridQuickSearchMode;
   /**
    * Highlights the matched text in cells while a contains-family column
-   * filter or the quick search is active. Default-rendered cells only — a
+   * filter or the quick search is active. Default-rendered cells only - a
    * column with its own `cell` renderer opts out by existing; a fuzzy
    * typo-match with no contiguous occurrence shows no highlight. Off by
    * default.
@@ -1599,8 +1599,8 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * | `"checkboxAndHighlight"` | yes, multi-select | highlights one row |
    * | `"highlight"` | no | highlights one row, no selection at all |
    *
-   * One option rather than two, so the combination that cannot work — a click
-   * that both toggles a multi-selection and moves the highlight — is not
+   * One option rather than two, so the combination that cannot work - a click
+   * that both toggles a multi-selection and moves the highlight - is not
    * expressible.
    *
    * The first two write to TanStack's `rowSelection`. The highlight is separate
@@ -1633,7 +1633,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * highlight. Read once on mount, like `initialState`.
    *
    * The grid never persists the highlighted row. Pair this with
-   * {@link onHighlightedRowChange} and keep it wherever it belongs — for a
+   * {@link onHighlightedRowChange} and keep it wherever it belongs - for a
    * detail panel that is usually the route, which gets you a shareable link and
    * a working back button as well as surviving a reload:
    *
@@ -1669,7 +1669,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * | PageUp / PageDown | one viewport of rows |
    * | Home / End | first / last cell of the row |
    * | Ctrl+Home / Ctrl+End | first / last cell of the grid |
-   * | Enter or F2 | into the cell — the checkbox, link or button it holds |
+   * | Enter or F2 | into the cell - the checkbox, link or button it holds |
    * | Escape | back out to the cell |
    * | Space | selects the row, as it does in row-selection mode |
    *
@@ -1679,7 +1679,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * | ------- | ---- |
    * | Drag across cells | selects the rectangle they span |
    * | Shift+click, Shift+arrows | extends the rectangle from its anchor |
-   * | Ctrl+C | copies it as tab-separated text — paste lands in Excel's cells |
+   * | Ctrl+C | copies it as tab-separated text - paste lands in Excel's cells |
    * | Right-click inside it | offers the CSV export, headers optional |
    *
    * Off, nothing about the body changes. On, three things do: the body's tab
@@ -1689,7 +1689,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * the cells take `data-focused` / `data-selected` for the ring and the tint.
    *
    * The state is `ui.state.focusedCell` and `ui.state.cellRange`, and moving it
-   * is `ui.actions.setFocusedCell` / `setCellRange` — so a consumer can put the
+   * is `ui.actions.setFocusedCell` / `setCellRange` - so a consumer can put the
    * keyboard on a cell, or follow it:
    *
    * ```tsx
@@ -1716,7 +1716,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * it is what turns row details on.
    *
    * Which rows are open is TanStack's own `expanded` state, so opening one is
-   * `row.toggleExpanded()` from wherever suits — a chevron in a cell, a button
+   * `row.toggleExpanded()` from wherever suits - a chevron in a cell, a button
    * in the context menu, a double-click:
    *
    * ```tsx
@@ -1727,7 +1727,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * });
    * ```
    *
-   * The panel is as tall as what it renders — see {@link renderDetailsEstHeight}
+   * The panel is as tall as what it renders - see {@link renderDetailsEstHeight}
    * for what the virtualizer assumes before it has measured one.
    *
    * Group rows are left out: expanding one opens its children, and a panel there
@@ -1746,7 +1746,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    *
    * An estimate, not a height: every mounted row is measured, so the real one
    * takes over as soon as the panel is on screen. It keeps the scrollbar honest
-   * for panels that open off screen — restored `expanded` state, say — and being
+   * for panels that open off screen (restored `expanded` state, say), and being
    * roughly right is enough.
    */
   renderDetailsEstHeight?: number;
@@ -1754,7 +1754,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
    * Rows the virtualizer keeps mounted above and below the viewport. Defaults
    * to 6.
    *
-   * Raise it to trade memory for a scroll that stays painted — fast wheel or
+   * Raise it to trade memory for a scroll that stays painted - fast wheel or
    * touch flings can outrun the virtualizer and flash blank rows, and a larger
    * buffer covers the gap. Lower it when rows are expensive to render.
    */
@@ -1765,7 +1765,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
  *
  * Every `TableOptions` field passes straight through, so a server-driven grid
  * only needs `manualPagination` / `manualFiltering` / `manualSorting`,
- * `rowCount` and the matching `onXChange` callbacks — the chrome reads
+ * `rowCount` and the matching `onXChange` callbacks - the chrome reads
  * `getRowCount()` / `getPageCount()` / `getPaginatedRowModel()`, all of which
  * already respect manual mode. `manualPagination` also switches the pagination
  * flag on, so `<TMDataGrid.Footer />` renders its pager without further
@@ -1774,7 +1774,7 @@ type UseTMDataGridOptions<TData extends RowData> = Omit<TableOptions<TMDataGridF
 declare function useTMDataGrid<TData extends RowData>({ persist, labels: labelsOverride, enableColumnOrdering, enablePagination, enableRowNumbers, selectionMode, showSelectedBackground, defaultHighlightedRowId, onHighlightedRowChange, cellSelection, onFocusedCellChange, editMode, rowValidators, isRowEditable, onEditCommit, onEditCommitBatch, newRowDefaults, onRowAdd, onRowDelete, renderDetails, renderDetailsEstHeight, overscan, ...options }: UseTMDataGridOptions<TData>): TMDataGridApi<TData>;
 /**
  * Opens the filter panel for a column, seeding an empty filter row when the
- * column has none yet — mirrors "Filter" in the column header menu.
+ * column has none yet - mirrors "Filter" in the column header menu.
  */
 declare function openColumnFilter<TData extends RowData>(api: TMDataGridApi<TData>, columnId: string): void;
 //#endregion
@@ -1794,7 +1794,7 @@ type TMDataGridFilterPillsProps<TData extends RowData> = {
   className?: string;
 };
 /**
- * One pill per active filter — `First name: Sofia ✕` — with the ✕ clearing that
+ * One pill per active filter (`First name: Sofia ✕`), with the ✕ clearing that
  * filter and a click on the label opening the filter panel on its column.
  *
  * The one grid component that takes the api as a prop instead of reading
@@ -1847,11 +1847,11 @@ type TMDataGridFooterProps = {
  * MUI-style pager: "Rows per page · from–to of total · ‹ ›".
  *
  * Renders nothing unless pagination is enabled (`enablePagination` or
- * `manualPagination`) — the footer is a pager; extra footer content belongs in
+ * `manualPagination`) - the footer is a pager; extra footer content belongs in
  * your own layout.
  *
  * Row totals come from `table.getRowCount()`, which prefers `options.rowCount`
- * — so a server-paged grid shows the server's total without changes here.
+ * - so a server-paged grid shows the server's total without changes here.
  */
 declare function TMDataGridFooter({ pageSizeOptions, pagination }: TMDataGridFooterProps): import("react").JSX.Element | null;
 //#endregion
@@ -1861,7 +1861,7 @@ type TMDataGridSearchProps = {
   placeholder?: string;
   /**
    * How long typing pauses before the filter is applied, in ms. Defaults to
-   * 250. `0` writes on every keystroke — what the tests use, and fine for
+   * 250. `0` writes on every keystroke - what the tests use, and fine for
    * small client-side data sets.
    */
   debounce?: number;
@@ -1869,7 +1869,7 @@ type TMDataGridSearchProps = {
   w?: number | string;
 };
 /**
- * Quick search over every column — a debounced input writing the table's
+ * Quick search over every column - a debounced input writing the table's
  * `globalFilter` state through the `"includesString"` filter the grid
  * configures by default.
  *
@@ -1882,12 +1882,12 @@ type TMDataGridSearchProps = {
  * ```
  *
  * Renders nothing under `enableGlobalFilter: false`. Columns opt out with
- * their own `enableGlobalFilter: false` — the generated lanes already do.
+ * their own `enableGlobalFilter: false` - the generated lanes already do.
  *
  * The state is TanStack's `globalFilter`, so everything around it comes free:
  * `manualFiltering` grids forward it to the server, and it is one of the
  * persisted `data` slices. A grid that wants its own input entirely writes
- * `table.setGlobalFilter` itself — this component is only the built-in one.
+ * `table.setGlobalFilter` itself - this component is only the built-in one.
  */
 declare function TMDataGridSearch({ placeholder, debounce, w }: TMDataGridSearchProps): import("react").JSX.Element | null;
 //#endregion
@@ -1928,7 +1928,7 @@ declare function formatExportValue(value: unknown, { decimalComma }: {
 }): string;
 type BuildCellMatrixArgs = {
   rows: ReadonlyArray<Row<TMDataGridFeatures, TMDataGridRowData>>;
-  /** Every visible column, in render order — the same list the bounds index into. */
+  /** Every visible column, in render order - the same list the bounds index into. */
   columns: ReadonlyArray<Column<TMDataGridFeatures, TMDataGridRowData, unknown>>;
   bounds: TMDataGridRangeBounds;
   includeHeaders: boolean;
@@ -1937,20 +1937,20 @@ type BuildCellMatrixArgs = {
 /**
  * The selected rectangle as rows of text.
  *
- * The generated lanes — the checkbox, the tree chevron, the details chevron —
+ * The generated lanes - the checkbox, the tree chevron, the details chevron -
  * are dropped even when the rectangle covers them. They hold controls rather
  * than data, so a column of empty strings is all they could contribute, and
  * pasting one into a spreadsheet only shifts everything to its right.
  */
 declare function buildCellMatrix({ rows, columns, bounds, includeHeaders, decimalComma }: BuildCellMatrixArgs): TMDataGridCellMatrix;
 /**
- * The whole grid as rows of text: every filtered and sorted data row — all
- * pages, not the one on screen — by every visible non-control column, in
+ * The whole grid as rows of text: every filtered and sorted data row - all
+ * pages, not the one on screen - by every visible non-control column, in
  * render order.
  *
  * The values are the same ones a cell-range export writes; only the bounds
  * differ. Group rows are left out (their records are the rows themselves),
- * and hidden columns are not exported — what you see is what you get, minus
+ * and hidden columns are not exported - what you see is what you get, minus
  * paging.
  */
 declare function buildGridCellMatrix<TData extends RowData>({ table, includeHeaders, decimalComma }: {
@@ -1959,7 +1959,7 @@ declare function buildGridCellMatrix<TData extends RowData>({ table, includeHead
   decimalComma?: boolean;
 }): TMDataGridCellMatrix;
 /**
- * Downloads the whole grid as a CSV for Excel — {@link buildGridCellMatrix}
+ * Downloads the whole grid as a CSV for Excel - {@link buildGridCellMatrix}
  * through {@link toExcelCsv}, with the same Nordic defaults and overrides as
  * the cell-range export.
  *
@@ -1977,7 +1977,7 @@ declare function exportGridToCsv<TData extends RowData>({ table, options }: {
  * The clipboard format spreadsheets read: tab between cells, CRLF between rows.
  *
  * Tabs rather than commas because that is what Excel, Sheets and Numbers all
- * put on the clipboard themselves — paste it and the cells land in cells. A
+ * put on the clipboard themselves - paste it and the cells land in cells. A
  * comma-separated string pastes into a single column, which is the thing this
  * exists to avoid.
  */
@@ -1989,12 +1989,12 @@ declare function toClipboardText(matrix: TMDataGridCellMatrix): string;
  *
  * | Part | Why |
  * | ---- | --- |
- * | `sep=;` first line | Excel's own directive — it stops guessing and uses this |
+ * | `sep=;` first line | Excel's own directive - it stops guessing and uses this |
  * | UTF-8 BOM | without it Excel reads the file as ANSI, and å ä ö arrive broken |
  * | CRLF line endings | what Excel writes, and what its importer is happiest with |
  *
  * The `sep=` line is Excel's alone; other readers show it as a first row. That
- * is the trade this makes — the file is for Excel, and "it just opens" is worth
+ * is the trade this makes - the file is for Excel, and "it just opens" is worth
  * more than being a well-behaved CSV nobody was going to feed to a parser.
  */
 declare function toExcelCsv(matrix: TMDataGridCellMatrix, { separator }: {
@@ -2004,14 +2004,14 @@ declare function toExcelCsv(matrix: TMDataGridCellMatrix, { separator }: {
  * Puts text on the clipboard, reporting whether it landed.
  *
  * The async clipboard API only resolves for a document that has the focus and a
- * user gesture behind it — both true when this runs off Ctrl+C or a menu item.
+ * user gesture behind it - both true when this runs off Ctrl+C or a menu item.
  * It is still allowed to reject (a permissions policy, a page that lost focus
  * mid-copy), so the result is a boolean rather than a promise nobody checks.
  */
 declare function writeClipboardText(text: string): Promise<boolean>;
 /**
  * Downloads text as a file, through the one mechanism a library can use: an
- * anchor with an object URL behind it, clicked. Revoked on the next frame —
+ * anchor with an object URL behind it, clicked. Revoked on the next frame -
  * immediately would race the browser's own read of it.
  */
 declare function downloadTextFile({ fileName, text, mimeType }: {
@@ -2026,12 +2026,12 @@ type TMDataGridColumnLayout = {
   pinnedAt: "left" | "right" | false;
   /** Distance in px from the grid's left or right edge. */
   offset: number;
-  /** Last left-pinned / first right-pinned column — the one that casts the edge. */
+  /** Last left-pinned / first right-pinned column - the one that casts the edge. */
   isBoundary: boolean;
 };
 /**
  * What a cell needs to take part in cell selection, or `undefined` while the
- * feature is off — which is what keeps a plain grid's cells exactly as they
+ * feature is off - which is what keeps a plain grid's cells exactly as they
  * were: no tab stop, no `gridcell` role, no coordinates in the DOM.
  *
  * The coordinates are there for the delegated key handler, which reads them off
@@ -2049,7 +2049,7 @@ type TMDataGridCellNav = {
   selected: boolean;
   /**
    * Which sides of the rectangle this cell is on, or `null` when it is not in
-   * one. The outline is drawn per cell — see {@link boundsEdges}.
+   * one. The outline is drawn per cell - see {@link boundsEdges}.
    */
   edges: {
     top: boolean;
@@ -2064,7 +2064,7 @@ type TMDataGridRowContextMenuArgs<TData extends RowData> = {
   row: Row<TMDataGridFeatures, TData>;
   /**
    * The cell under the pointer. `null` only when the right-click landed on the
-   * row but on no cell — which a custom cell renderer that stops propagation
+   * row but on no cell - which a custom cell renderer that stops propagation
    * can cause.
    */
   cell: Cell<TMDataGridFeatures, TData, unknown> | null;
@@ -2075,13 +2075,13 @@ type TMDataGridRowContextMenuArgs<TData extends RowData> = {
   close: () => void;
 };
 /**
- * Builds the contents of a row's context menu — `Menu.Item`, `Menu.Label`,
+ * Builds the contents of a row's context menu - `Menu.Item`, `Menu.Label`,
  * `Menu.Divider`, `Menu.Sub`, or any other node. The grid owns the `Menu` and
  * its `Menu.Dropdown`; this fills the dropdown.
  */
 type TMDataGridRowContextMenu<TData extends RowData> = (args: TMDataGridRowContextMenuArgs<TData>) => ReactNode;
 /**
- * What the `onCellClick` family receives — the cell with its row and column,
+ * What the `onCellClick` family receives - the cell with its row and column,
  * in the consumer's own row type, plus the pointer event.
  */
 type TMDataGridCellEventArgs<TData extends RowData> = {
@@ -2092,7 +2092,7 @@ type TMDataGridCellEventArgs<TData extends RowData> = {
 };
 /**
  * Inline styles for a row. Widened to accept CSS variables, because setting
- * `--row-bg` is the supported way to colour a row — see {@link
+ * `--row-bg` is the supported way to colour a row - see {@link
  * TMDataGridTableProps.rowStyle}.
  */
 type TMDataGridRowStyle = CSSProperties | (CSSProperties & Record<`--${string}`, string | number>);
@@ -2104,8 +2104,8 @@ type TMDataGridTableProps<TData extends RowData> = {
   onRowClick?: (row: Row<TMDataGridFeatures, TData>) => void;
   /**
    * Called when a body cell is clicked. Composes, never suppresses: whatever
-   * the click already does — selecting, highlighting, moving the cell cursor
-   * — still happens. Group rows sit out the cell handlers the way they sit
+   * the click already does - selecting, highlighting, moving the cell cursor
+   * - still happens. Group rows sit out the cell handlers the way they sit
    * out `onRowClick`, and for the same reason.
    */
   onCellClick?: (args: TMDataGridCellEventArgs<TData>) => void;
@@ -2118,7 +2118,7 @@ type TMDataGridTableProps<TData extends RowData> = {
    */
   onCellContextMenu?: (args: TMDataGridCellEventArgs<TData>) => void;
   /**
-   * Class for a body row — a string, or a function of the row (group rows
+   * Class for a body row - a string, or a function of the row (group rows
    * included; test `row.getIsGrouped()` to skip them). Added after the grid's
    * own row class.
    */
@@ -2127,7 +2127,7 @@ type TMDataGridTableProps<TData extends RowData> = {
    * Inline style for a body row. To colour a row, set `--row-bg` rather than
    * `background`: the row's own background, its sticky pinned cells and the
    * cell-range tint all read that variable, and hover/selection/highlight
-   * keep working on top of it — a raw `background` bypasses all of them.
+   * keep working on top of it - a raw `background` bypasses all of them.
    *
    * ```tsx
    * rowStyle={(row) =>
@@ -2138,12 +2138,12 @@ type TMDataGridTableProps<TData extends RowData> = {
   rowStyle?: TMDataGridRowStyle | ((row: Row<TMDataGridFeatures, TData>) => TMDataGridRowStyle | undefined);
   /**
    * Every second row takes `--dg-row-striped-bg`. Computed from the row's
-   * position in the view — sorting and filtering restripe, and the stripes
+   * position in the view - sorting and filtering restripe, and the stripes
    * stay put while the virtualizer mounts and unmounts rows.
    */
   striped?: boolean;
   /**
-   * Called when the scroll *arrives* at an edge — once per arrival, not per
+   * Called when the scroll *arrives* at an edge - once per arrival, not per
    * scroll event, and not on mount (the grid starts at the top-left edge).
    * For loading more rows as the end approaches, `onReachEnd` is the better
    * hook: it fires rows-early and latches per row count.
@@ -2156,10 +2156,10 @@ type TMDataGridTableProps<TData extends RowData> = {
   /** As {@link onScrollToTop}, for the right edge. */
   onScrollToRight?: () => void;
   /**
-   * Rendered centred in the body when the view is empty — the branded blank
+   * Rendered centred in the body when the view is empty - the branded blank
    * slate. It takes over states 3 and 4 of the empty matrix (see the docs):
    * loading still shows the loader, and open entry rows still show only
-   * themselves. `hasActiveFilters` says which emptiness this is — a filter
+   * themselves. `hasActiveFilters` says which emptiness this is - a filter
    * that matched nothing wants a "clear filters" invitation, a grid with no
    * data wants a "create the first one".
    */
@@ -2169,7 +2169,7 @@ type TMDataGridTableProps<TData extends RowData> = {
   }) => ReactNode;
   /**
    * Contents of the menu a right-click on a row opens, at the pointer. Return
-   * `null` to leave a row without one — the browser's own menu stays suppressed
+   * `null` to leave a row without one - the browser's own menu stays suppressed
    * either way.
    *
    * ```tsx
@@ -2187,23 +2187,23 @@ type TMDataGridTableProps<TData extends RowData> = {
    * />
    * ```
    *
-   * Called during render, and only for the row whose menu is open — so it stays
+   * Called during render, and only for the row whose menu is open - so it stays
    * a pure function of the row, and cost per row does not matter.
    */
   rowContextMenu?: TMDataGridRowContextMenu<TData>;
   /**
-   * Passed to the Mantine `Menu` the grid wraps the row in — `width`, `shadow`,
+   * Passed to the Mantine `Menu` the grid wraps the row in - `width`, `shadow`,
    * `position`, `transitionProps` and the rest. Its open state is the grid's.
    */
   rowContextMenuProps?: Omit<MenuProps, "opened" | "onChange" | "children">;
   /**
    * How Ctrl+C and the export item write values, under
-   * `cellSelection: "range"`. Defaults to the Nordic Excel conventions — see
+   * `cellSelection: "range"`. Defaults to the Nordic Excel conventions - see
    * {@link TMDataGridCellExportOptions}.
    */
   cellExport?: TMDataGridCellExportOptions;
   /**
-   * Called when the scroll approaches the last row — the infinite-scroll
+   * Called when the scroll approaches the last row - the infinite-scroll
    * hook-in. Append the next page to `data` and the virtualizer keeps its
    * position; fires once per row count, so a pending fetch is not asked
    * again until it lands.
@@ -2213,7 +2213,7 @@ type TMDataGridTableProps<TData extends RowData> = {
    * ```
    *
    * Sorting and filtering must be server-side (`manual*`) on a grid that
-   * loads this way — the client only ever holds a prefix of the data. Not
+   * loads this way - the client only ever holds a prefix of the data. Not
    * compatible with `enablePagination`, which slices the same scroll.
    */
   onReachEnd?: () => void;
@@ -2222,7 +2222,7 @@ type TMDataGridTableProps<TData extends RowData> = {
    */
   reachEndThreshold?: number;
   /**
-   * Accessible name for the grid — what a screen reader announces on entry,
+   * Accessible name for the grid - what a screen reader announces on entry,
    * and what `getByRole("grid", { name })` matches. Worth setting on any page
    * holding more than one grid; without it they are all just "grid".
    */
@@ -2232,7 +2232,7 @@ type TMDataGridTableProps<TData extends RowData> = {
 };
 /**
  * The scrollable grid surface. Always virtualized: only the rows inside the
- * viewport (plus overscan) are mounted — which is what makes the default
+ * viewport (plus overscan) are mounted - which is what makes the default
  * no-pagination mode viable at any row count. Pagination is opt-in via
  * `enablePagination` (or implied by `manualPagination`).
  */
@@ -2248,7 +2248,7 @@ declare function TMDataGridToolbarSpacer(): import("react").JSX.Element;
 /**
  * A small spinner shown while `meta.loading` is true, and nothing otherwise.
  *
- * The body only shows its loading state while the grid is *empty* — a
+ * The body only shows its loading state while the grid is *empty* - a
  * server-driven grid refetching with rows on screen keeps showing them, which
  * is right, but leaves nothing saying a fetch is running. This is that signal,
  * and the consumer decides where it sits by placing it in the toolbar:
@@ -2265,13 +2265,13 @@ declare function TMDataGridToolbarSpacer(): import("react").JSX.Element;
 declare function TMDataGridLoadingIndicator(): import("react").JSX.Element | null;
 /**
  * Visible rows over total rows. On a server-driven grid, set
- * `meta.totalRowCount` for the denominator — the client never sees every row.
+ * `meta.totalRowCount` for the denominator - the client never sees every row.
  */
 declare function TMDataGridSummaryCount({ children }: {
   children?: ReactNode;
 }): import("react").JSX.Element;
 /**
- * Burger menu in the grid's top-right corner — opens "Manage columns".
+ * Burger menu in the grid's top-right corner - opens "Manage columns".
  * Renders nothing when no column can be hidden (`enableHiding: false`).
  */
 declare function TMDataGridColumnsButton(): import("react").JSX.Element | null;
@@ -2292,7 +2292,7 @@ type TMDataGridProps<TData extends RowData> = TMDataGridApi<TData> & {
   className?: string;
   /**
    * Inline styles. Widened to accept CSS variables, which is how the grid's
-   * colours are themed — `--dg-row-selected-bg` for the selected row
+   * colours are themed - `--dg-row-selected-bg` for the selected row
    * background. Plain `CSSProperties` rejects `--*` keys.
    */
   style?: CSSProperties & Record<`--${string}`, string | number>;
@@ -2301,7 +2301,7 @@ type TMDataGridProps<TData extends RowData> = TMDataGridApi<TData> & {
   /**
    * Names this grid for tests. The grid names its own pieces with
    * `data-dg-part` rather than minting test ids, and those repeat across
-   * grids — scope through this one and they stop colliding:
+   * grids - scope through this one and they stop colliding:
    *
    * ```ts
    * page.getByTestId("orders").locator('[data-dg-part="row"][data-row-id="42"]')
@@ -2312,7 +2312,7 @@ type TMDataGridProps<TData extends RowData> = TMDataGridApi<TData> & {
   "data-testid"?: string;
 };
 /**
- * Root of the grid. Takes the object returned by `useTMDataGrid` — spread it —
+ * Root of the grid. Takes the object returned by `useTMDataGrid` - spread it -
  * and publishes it to the compound components below it:
  *
  * ```tsx
@@ -2345,7 +2345,7 @@ declare const TMDataGrid: typeof TMDataGridRoot & {
   FilterPanel: typeof TMDataGridFilterPanel;
   /**
    * Takes the grid as an `api` prop rather than from context, so it can be
-   * rendered outside `<TMDataGrid>` — a page header, for instance.
+   * rendered outside `<TMDataGrid>` - a page header, for instance.
    */
   FilterPills: typeof TMDataGridFilterPills;
   /** Rendered by `TMDataGrid.ColumnsButton`; exported for custom layouts. */
@@ -2377,7 +2377,7 @@ declare function formatGroupValue(value: unknown, blankLabel?: string): string;
 //#endregion
 //#region .types-tmp/components/filters/TMDataGridFilterValueInput.d.ts
 /**
- * The built-in value control of a filter-panel row — what renders when a
+ * The built-in value control of a filter-panel row - what renders when a
  * column declares no `meta.filterControl`. Shaped by the operator: a
  * multi-select for the set operators, a From/To pair for `between`, a Yes/No
  * dropdown for booleans, a typed input otherwise.
@@ -2400,7 +2400,7 @@ declare function DgRangeSliderFilter(args: TMDataGridFilterControlArgs): import(
 //#region .types-tmp/components/filters/DgDateRangeFilter.d.ts
 /**
  * A built-in `meta.filterControl` for `date` columns: a From/To pair of
- * native date inputs writing the `between` pair — no `@mantine/dates`
+ * native date inputs writing the `between` pair - no `@mantine/dates`
  * involved, like the built-in date editor. Pair it with
  * `meta.defaultFilterOperator: "between"`; any non-range operator falls back
  * to the standard input.
@@ -2419,7 +2419,7 @@ declare function DgAutocompleteFilter(args: TMDataGridFilterControlArgs): import
 //#region .types-tmp/components/filters/DgTriStateFilter.d.ts
 /**
  * A built-in `meta.filterControl` for `boolean` columns: an All / Yes / No
- * segmented control — All clears the value, which deactivates the filter.
+ * segmented control - All clears the value, which deactivates the filter.
  * Set or range operators fall back to the standard input.
  */
 declare function DgTriStateFilter(args: TMDataGridFilterControlArgs): import("react").JSX.Element;
@@ -2433,12 +2433,12 @@ declare function TMDataGridStringEditor({ field, autoFocus, column, size }: TMDa
 declare function TMDataGridNumberEditor({ field, autoFocus, column, size }: TMDataGridEditorArgs): import("react").JSX.Element;
 //#endregion
 //#region .types-tmp/components/editors/TMDataGridBooleanEditor.d.ts
-/** The built-in editor for `meta.type: "boolean"` — a focused checkbox. */
+/** The built-in editor for `meta.type: "boolean"` - a focused checkbox. */
 declare function TMDataGridBooleanEditor({ field, autoFocus, column, size }: TMDataGridEditorArgs): import("react").JSX.Element;
 //#endregion
 //#region .types-tmp/components/editors/TMDataGridDateEditor.d.ts
 /**
- * The built-in editor for `meta.type: "date"` — the native
+ * The built-in editor for `meta.type: "date"` - the native
  * `<input type="date">` styled by Mantine, no `@mantine/dates` involved. A
  * consumer wanting a real picker plugs one in through `meta.editor`.
  */
@@ -2447,14 +2447,14 @@ declare function TMDataGridDateEditor({ field, autoFocus, column, size }: TMData
 //#region .types-tmp/components/editors/TMDataGridSelectEditor.d.ts
 /**
  * The built-in editor for `meta.type: "select"`. Options come from the same
- * `meta.options` the filter panel reads — with the row in hand, so a
+ * `meta.options` the filter panel reads - with the row in hand, so a
  * function source can depend on the record being edited.
  */
 declare function TMDataGridSelectEditor({ field, autoFocus, column, row, table, size, commit }: TMDataGridEditorArgs): import("react").JSX.Element;
 //#endregion
 //#region .types-tmp/components/editors/TMDataGridMultiSelectEditor.d.ts
 /**
- * The built-in editor for `meta.type: "multiSelect"` — cells holding string
+ * The built-in editor for `meta.type: "multiSelect"` - cells holding string
  * arrays. Never commits on pick: building a set takes several, so the commit
  * stays on Enter/blur like a text edit.
  */
@@ -2492,18 +2492,18 @@ type ColumnLike = {
 declare function getColumnLabel(column: ColumnLike): string;
 declare function getColumnType(column: ColumnLike): TMDataGridColumnType;
 /**
- * The operator a fresh filter on this column starts with —
+ * The operator a fresh filter on this column starts with -
  * `meta.defaultFilterOperator`, else the type's default.
  */
 declare function getColumnDefaultOperator(column: ColumnLike): TMDataGridFilterOperator;
 /**
- * A generated lane holding one fixed-width thing — the checkbox, the details
+ * A generated lane holding one fixed-width thing - the checkbox, the details
  * chevron, the row number.
  *
  * They are laid out differently from every other column: cell padding is sized
  * for text and grows with the scale, which at `xl` squeezed a 16px checkbox out
  * of its track, so these lanes centre their content in an unpadded cell.
- * Their headers carry no column menu, and none of them is ever exported —
+ * Their headers carry no column menu, and none of them is ever exported -
  * they hold chrome, not values.
  *
  * The tree column is deliberately not one of them: it holds a label as well as a
@@ -2536,10 +2536,10 @@ declare function isColumnReorderable(column: ColumnLike): boolean;
 declare function getGroupDataRows<TData extends RowData>(row: Row<TMDataGridFeatures, TData>): Array<Row<TMDataGridFeatures, TData>>;
 //#endregion
 //#region .types-tmp/core/summary.d.ts
-/** The registered aggregation names — the same set `aggregationFn` accepts. */
+/** The registered aggregation names - the same set `aggregationFn` accepts. */
 type TMDataGridAggregationName = keyof typeof aggregationFns;
 /**
- * One column aggregated over every filtered row — the number a summary-row
+ * One column aggregated over every filtered row - the number a summary-row
  * `footer` wants:
  *
  * ```tsx
@@ -2549,7 +2549,7 @@ type TMDataGridAggregationName = keyof typeof aggregationFns;
  * ```
  *
  * Filtered rather than paginated rows, so the total covers everything the
- * filters left — all pages — and follows the filters as they change. Reuses
+ * filters left (all pages), and follows the filters as they change. Reuses
  * TanStack's registered aggregation functions; `fn` defaults to `"sum"`.
  */
 declare function aggregateColumn<TData extends RowData>({ table, columnId, fn }: {
@@ -2563,16 +2563,16 @@ declare function aggregateColumn<TData extends RowData>({ table, columnId, fn }:
  * Widest rendered content of one column, in px, measured from the DOM.
  *
  * Mounted cells only: under virtualization the unmounted rows do not exist to
- * be measured, so this reads the visible window plus overscan — the same
+ * be measured, so this reads the visible window plus overscan - the same
  * trade AG Grid's autosize makes by default.
  */
 declare function measureColumnContentWidth({ container, columnId }: {
-  /** The grid's scroll container — anything enclosing the column's cells. */
+  /** The grid's scroll container - anything enclosing the column's cells. */
   container: HTMLElement;
   columnId: string;
 }): number;
 /**
- * Sizes a column to its widest mounted content — what double-clicking the
+ * Sizes a column to its widest mounted content - what double-clicking the
  * resize divider does, exported so a menu item or consumer code can trigger
  * the same thing.
  *
@@ -2593,8 +2593,8 @@ declare function autosizeColumn<TData extends RowData>({ table, columnId, contai
  *
  * TanStack keeps one `expanded` state, and the grid opens two unrelated things
  * out of it: a group row opens into its children, a data row opens into its
- * detail panel. So `toggleAllRowsExpanded` — which writes the state's
- * whole-table form — is the wrong verb for either control. "Expand all groups"
+ * detail panel. So `toggleAllRowsExpanded` - which writes the state's
+ * whole-table form - is the wrong verb for either control. "Expand all groups"
  * in the tree menu would open every panel in the grid, and the details lane's
  * chevron would unfold the whole tree.
  *
@@ -2604,7 +2604,7 @@ declare function autosizeColumn<TData extends RowData>({ table, columnId, contai
 type TMDataGridExpandTarget = "groups" | "details";
 type TMDataGridExpandAllArgs<TData extends RowData> = {
   /**
-   * Every row in the model, groups and records alike — `flatRows` off any of
+   * Every row in the model, groups and records alike - `flatRows` off any of
    * them. A grouped model lists its leaves both under their group and in the
    * flat list, so this may repeat rows; both helpers are written so that a
    * repeat costs nothing.
@@ -2614,7 +2614,7 @@ type TMDataGridExpandAllArgs<TData extends RowData> = {
   target: TMDataGridExpandTarget;
 };
 /**
- * Whether every row of this kind is open — what the control shows, and what a
+ * Whether every row of this kind is open - what the control shows, and what a
  * bare toggle inverts.
  *
  * `false` when there are none of them, matching TanStack's own
@@ -2639,7 +2639,7 @@ type GridTable = TMDataGridTable<TMDataGridRowData>;
  * Pinning splits the grid into three, and TanStack sequences them from two
  * different state slices: `columnPinning.left` / `.right` order the pinned
  * lanes, `columnOrder` orders the centre. A move therefore always stays inside
- * one lane — moving a column into another one would be a pin, not a reorder.
+ * one lane - moving a column into another one would be a pin, not a reorder.
  */
 type TMDataGridColumnRegion = "left" | "center" | "right";
 /** Which edge of the column under the pointer a dragged column lands on. */
@@ -2673,7 +2673,7 @@ type ColumnStepArgs = {
  * The column a single step would swap with, or `null` when there is none.
  *
  * A neighbour that cannot be reordered acts as a wall rather than being skipped
- * — that is what keeps the checkbox column anchored at the start of the left
+ * - that is what keeps the checkbox column anchored at the start of the left
  * lane. Use it to enable or disable a "move" control.
  */
 declare function getStepTargetColumn({ table, columnId, direction }: ColumnStepArgs): GridColumn | null;
@@ -2683,17 +2683,17 @@ declare function moveColumnByStep({ table, columnId, direction }: ColumnStepArgs
 //#region .types-tmp/core/rowSelection.d.ts
 /**
  * Rows in the order they are displayed, which is the order a shift-click range
- * is measured over — so a range follows the active sort and skips filtered-out
+ * is measured over - so a range follows the active sort and skips filtered-out
  * rows. Under pagination it is the current page, so a range cannot cross a page
  * boundary.
  *
  * Once a column is grouped this includes the group rows, and only the leaves of
- * groups that are open — and paging is suspended, so it is the whole tree. That
+ * groups that are open - and paging is suspended, so it is the whole tree. That
  * is the right list for a range: it is what the user can see, and a range that
  * swept collapsed rows would select things off screen. What a group row in the
  * range contributes is decided by {@link getSelectableRowIds}.
  *
- * Rows pinned to an edge leave this list — they render in their own sticky
+ * Rows pinned to an edge leave this list - they render in their own sticky
  * blocks, outside the scrolling order a shift-click range or the virtualizer
  * walks. See `readPinnedRows`.
  */
@@ -2707,7 +2707,7 @@ declare function getDisplayedRows<TData extends RowData>(table: TMDataGridTable<
  * to go looking for, and counting only the top-level rows quietly redefines
  * "rows per page" as groups per page, so a page of 25 can hold thousands of
  * rows. Rather than pick, the grid renders the whole tree and leans on the
- * virtualizer — which is its default mode anyway, pagination being opt-in.
+ * virtualizer - which is its default mode anyway, pagination being opt-in.
  *
  * `TMDataGrid.Footer` reads this too, and greys the pager out rather than
  * hiding it, so the pager going quiet is visible instead of mysterious.
@@ -2715,7 +2715,7 @@ declare function getDisplayedRows<TData extends RowData>(table: TMDataGridTable<
 declare function isPagingActive<TData extends RowData>(table: TMDataGridTable<TData>, features: TMDataGridFeatureFlags): boolean;
 /**
  * Which modifiers were held. Named for what they mean rather than for the keys,
- * because the keys differ per platform — `toggle` is Ctrl on Windows/Linux and
+ * because the keys differ per platform - `toggle` is Ctrl on Windows/Linux and
  * Cmd on macOS.
  */
 type TMDataGridRowClickModifiers = {
@@ -2723,7 +2723,7 @@ type TMDataGridRowClickModifiers = {
   extend: boolean;
 };
 type ResolveRowSelectionClickArgs<TData extends RowData> = {
-  /** Displayed order — see {@link getDisplayedRows}. */
+  /** Displayed order - see {@link getDisplayedRows}. */
   rows: ReadonlyArray<Row<TMDataGridFeatures, TData>>;
   rowId: string;
   /** The pivot a shift-click extends from. */
@@ -2734,7 +2734,7 @@ type ResolveRowSelectionClickArgs<TData extends RowData> = {
    * Whether this gesture is allowed to clear rows it did not touch.
    *
    * `true` for a bare row click, where replacing is the whole point. `false` for
-   * a checkbox, which is only ever additive — ticking one box has never cleared
+   * a checkbox, which is only ever additive - ticking one box has never cleared
    * the others, and shift-clicking one adds the range rather than becoming it.
    */
   canReplaceSelection: boolean;