@jielga/tmdatagrid 1.0.0 → 1.0.1

package/src/tmdatagrid/components/TMDataGridToolbar.tsx

@@ -26,7 +26,7 @@ export function TMDataGridToolbarSpacer() {
 /**
  * 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:
@@ -48,7 +48,7 @@ export function TMDataGridLoadingIndicator() {
 
 /**
  * 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.
  */
 export function TMDataGridSummaryCount({ children }: { children?: ReactNode }) {
   const { table, controlSize } = useTMDataGridContext();
@@ -56,7 +56,7 @@ export function TMDataGridSummaryCount({ children }: { children?: ReactNode }) {
 
   if (children !== undefined) {
     return (
-      <Text size={controlSize} c="dimmed" data-dg-part="summary-count">
+      <Text span size={controlSize} c="dimmed" data-dg-part="summary-count">
         {children}
       </Text>
     );
@@ -68,14 +68,14 @@ export function TMDataGridSummaryCount({ children }: { children?: ReactNode }) {
     table.getPreFilteredRowModel().rows.length;
 
   return (
-    <Text size={controlSize} c="dimmed" data-dg-part="summary-count">
+    <Text span size={controlSize} c="dimmed" data-dg-part="summary-count">
       {shown} / {total}
     </Text>
   );
 }
 
 /**
- * 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`).
  */
 export function TMDataGridColumnsButton() {

package/src/tmdatagrid/components/editors/TMDataGridBooleanEditor.tsx

@@ -4,7 +4,7 @@ import { getColumnLabel } from "../../core/columnUtils";
 import { useTMDataGridContext } from "../../TMDataGridContext";
 import { useFieldError, useFieldValue } from "./editorShared";
 
-/** The built-in editor for `meta.type: "boolean"` — a focused checkbox. */
+/** The built-in editor for `meta.type: "boolean"` - a focused checkbox. */
 export function TMDataGridBooleanEditor({
   field,
   autoFocus,

package/src/tmdatagrid/components/editors/TMDataGridDateEditor.tsx

@@ -6,7 +6,7 @@ import { useTMDataGridContext } from "../../TMDataGridContext";
 import { useFieldError, useFieldValue } from "./editorShared";
 
 /**
- * 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`.
  */
@@ -20,7 +20,7 @@ export function TMDataGridDateEditor({
   const value = useFieldValue(field);
   const error = useFieldError(field);
   // The cell's original shape decides what the editor writes back: a `Date`
-  // cell keeps getting Dates, an ISO-string cell keeps getting strings —
+  // cell keeps getting Dates, an ISO-string cell keeps getting strings -
   // decided once at open, so clearing and retyping cannot flip the type.
   const writesDates = useRef(value instanceof Date);
 

package/src/tmdatagrid/components/editors/TMDataGridMultiSelectEditor.tsx

@@ -9,7 +9,7 @@ import { useTMDataGridContext } from "../../TMDataGridContext";
 import { useFieldError, useFieldValue } from "./editorShared";
 
 /**
- * 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.
  */

package/src/tmdatagrid/components/editors/TMDataGridNumberEditor.tsx

@@ -26,7 +26,7 @@ export function TMDataGridNumberEditor({
       value={typeof value === "number" ? value : ""}
       onChange={(next) =>
         // Mantine reports a number once one can be parsed, and a string while
-        // it cannot. An empty cell is `null` — the honest "no value".
+        // it cannot. An empty cell is `null` - the honest "no value".
         field.handleChange(
           typeof next === "number" ? next : next === "" ? null : Number(next),
         )

package/src/tmdatagrid/components/editors/TMDataGridSelectEditor.tsx

@@ -10,7 +10,7 @@ import { useFieldError, useFieldValue } from "./editorShared";
 
 /**
  * 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.
  */
 export function TMDataGridSelectEditor({
@@ -31,7 +31,7 @@ export function TMDataGridSelectEditor({
       w="100%"
       autoFocus={autoFocus}
       searchable
-      // Inside the cell, so picking an option is not a click-away — the same
+      // Inside the cell, so picking an option is not a click-away - the same
       // reason the filter panel keeps its dropdowns unportalled.
       comboboxProps={{ withinPortal: false }}
       aria-label={labels.editCell(getColumnLabel(column))}

package/src/tmdatagrid/components/editors/editorShared.ts

@@ -2,7 +2,7 @@ import { useStore } from "@tanstack/react-form";
 import type { TMDataGridEditField } from "../../core/editEngine";
 
 /**
- * The first error as text, whatever shape the validator produced — TanStack
+ * The first error as text, whatever shape the validator produced - TanStack
  * Form keeps errors verbatim, so a Zod issue arrives as `{ message }`, a
  * plain function's return arrives as it was, and a form-level schema's
  * pathless issues arrive keyed under an empty path (`{ "": [issues] }`).
@@ -29,7 +29,7 @@ export function firstErrorText(error: unknown): string | undefined {
   return undefined;
 }
 
-/** The field's live value — one subscription, on the field's own store. */
+/** The field's live value - one subscription, on the field's own store. */
 export function useFieldValue(field: TMDataGridEditField): unknown {
   return useStore(field.store, (state) => state.value as unknown);
 }
@@ -41,7 +41,7 @@ export function useFieldError(field: TMDataGridEditField): string | undefined {
   );
 }
 
-/** Select-all on focus — F2/Enter open with the value ready to replace. */
+/** Select-all on focus - F2/Enter open with the value ready to replace. */
 export function selectAllOnFocus(event: { currentTarget: unknown }): void {
   const target = event.currentTarget;
   if (target instanceof HTMLInputElement) target.select();

package/src/tmdatagrid/components/filters/DgDateRangeFilter.tsx

@@ -5,7 +5,7 @@ import { TMDataGridFilterValueInput } from "./TMDataGridFilterValueInput";
 
 /**
  * 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.

package/src/tmdatagrid/components/filters/DgRangeSliderFilter.tsx

@@ -16,7 +16,7 @@ export function DgRangeSliderFilter(args: TMDataGridFilterControlArgs) {
     return <TMDataGridFilterValueInput {...args} />;
   }
 
-  // Bounds from the faceted index — the min and max actually in the data.
+  // Bounds from the faceted index - the min and max actually in the data.
   const numbers: number[] = [];
   for (const key of column.getFacetedUniqueValues().keys()) {
     const numeric = Number(key);

package/src/tmdatagrid/components/filters/DgTriStateFilter.tsx

@@ -9,7 +9,7 @@ import { TMDataGridFilterValueInput } from "./TMDataGridFilterValueInput";
 
 /**
  * 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.
  */
 export function DgTriStateFilter(args: TMDataGridFilterControlArgs) {

package/src/tmdatagrid/components/filters/TMDataGridFilterValueInput.tsx

@@ -9,7 +9,7 @@ import {
 } from "../../core/filterOperators";
 
 /**
- * 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.
@@ -37,7 +37,7 @@ export function TMDataGridFilterValueInput({
       ? [String(value[0] ?? ""), String(value[1] ?? "")]
       : ["", ""];
     return (
-      // The interval's two ends. Either may stay empty — an open end — and
+      // The interval's two ends. Either may stay empty (an open end), and
       // each writes its slot of the `[min, max]` pair.
       <Group gap={4} wrap="nowrap" align="flex-start">
         <TextInput

package/src/tmdatagrid/components/sticky.module.css

@@ -1,9 +1,9 @@
 /* Boundary of a pinned column group. Shared, because the edge is cast by both
-   the header cell and every body cell in the same column — the two have to draw
+   the header cell and every body cell in the same column - the two have to draw
    an identical band or the seam shows at the header.
 
    A box-shadow is drawn per cell, and its blur fades in at each cell's own top
-   and bottom edge — stacked down a column that reads as banding at every row
+   and bottom edge - stacked down a column that reads as banding at every row
    seam. Instead: a gradient pseudo element pinned to `top: 0; bottom: 0` so
    consecutive cells butt together into one unbroken band. Mantine sets
    `color-scheme` on the root, so light-dark() resolves without a second
@@ -11,7 +11,7 @@
 
    No border. A 1px line the colour of the grid's own borders drew a hard rule
    between the pinned lanes and the data, so the pinned columns read as a
-   separate table rather than as part of this one — and at the system lanes,
+   separate table rather than as part of this one - and at the system lanes,
    which are only a control wide, it framed them like a sidebar. */
 .stickyLeft::after,
 .stickyRight::after {
@@ -24,7 +24,7 @@
 }
 
 /* Three stops rather than two. A straight linear ramp to `transparent` fades
-   fastest at the start, so its own outer edge stays visible as a faint line —
+   fastest at the start, so its own outer edge stays visible as a faint line -
    the sharpness a hard border was blamed for. Front-loading the falloff puts
    the density against the pinned cell and lets the tail reach zero unnoticed. */
 .stickyLeft::after {
@@ -53,12 +53,12 @@
 
    Driven by the scroll position itself rather than by a listener writing a
    class. A scroll-driven animation is evaluated on the compositor, so the band
-   tracks the scroll frame for frame without a single React render — and the
+   tracks the scroll frame for frame without a single React render - and the
    body re-renders on every scroll frame already, from virtualization.
 
    `scroll(nearest inline)` resolves to `.scrollContainer`, the one horizontal
-   scroller above these cells. An inactive timeline — which is what a container
-   with nothing to scroll gives — leaves the base style in place, so `opacity:
+   scroller above these cells. An inactive timeline - which is what a container
+   with nothing to scroll gives - leaves the base style in place, so `opacity:
    0` inside this block is also the answer for a grid that does not scroll. */
 @supports (animation-timeline: scroll()) {
   .stickyLeft::after,
@@ -79,7 +79,7 @@
 
   /* The mirror: on at rest, gone as the last column arrives. The range is
      measured from the end, and `both` holds the first value everywhere before
-     it — so the band stays fully on until the scroller is within 20px of home.
+     it - so the band stays fully on until the scroller is within 20px of home.
    */
   .stickyRight::after {
     animation-name: stickyEdgeOut;

package/src/tmdatagrid/core/autosize.ts

@@ -18,7 +18,7 @@ const CONTENT_ALLOWANCE = 2;
  * A Range over the children rather than the span's `scrollWidth`, because the
  * two disagree in opposite directions: a left-aligned cell stretches its
  * content span to fill the cell (`flex: 1 1 auto`), so `scrollWidth` reports
- * the stretched box and autosize could never *shrink* a column — while for
+ * the stretched box and autosize could never *shrink* a column - while for
  * clipped content both see past the `overflow: hidden`. The Range measures
  * the laid-out text and elements themselves, whatever box they sit in.
  *
@@ -41,14 +41,14 @@ function contentSpanWidth(content: HTMLElement): number {
  * 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.
  */
 export 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 {
@@ -91,7 +91,7 @@ export function measureColumnContentWidth({
 }
 
 /**
- * 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.
  *

package/src/tmdatagrid/core/capabilities.ts

@@ -21,10 +21,10 @@ import type {
  * 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.
@@ -36,11 +36,11 @@ export 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
@@ -58,7 +58,7 @@ export type TMDataGridCellSelectionMode =
 export 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;
@@ -73,7 +73,7 @@ export 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.
@@ -84,14 +84,14 @@ export 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.
    */
@@ -109,7 +109,7 @@ export 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
@@ -118,14 +118,14 @@ export 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.
@@ -133,7 +133,7 @@ export 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;
@@ -205,7 +205,7 @@ export function readFeatureFlags<TData extends RowData>(
     editing: options.editMode !== undefined,
     editMode: options.editMode ?? null,
     rowNumbers: options.enableRowNumbers === true,
-    // A predicate counts as on — some rows may still pin.
+    // A predicate counts as on - some rows may still pin.
     rowPinning:
       options.enableRowPinning === true ||
       typeof options.enableRowPinning === "function",
@@ -246,7 +246,7 @@ export function getColumnCapabilities(
     canHide: features.hiding && column.getCanHide(),
     canPin: features.pinning && column.getCanPin(),
     canResize: features.resizing && column.getCanResize(),
-    // Ordering has no TanStack capability method — see isColumnReorderable.
+    // Ordering has no TanStack capability method - see isColumnReorderable.
     canReorder: features.ordering && isColumnReorderable(column),
     // `getCanGroup()` also insists on an accessor, which is what keeps the
     // generated checkbox and tree columns from offering to group on themselves.
@@ -254,7 +254,7 @@ export function getColumnCapabilities(
   };
 }
 
-/** 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. */
 export type TMDataGridCapabilities = {
   canSortAny: boolean;
   canFilterAny: boolean;

package/src/tmdatagrid/core/cellExport.ts

@@ -71,7 +71,7 @@ export function formatExportValue(
       .map((entry) => formatExportValue(entry, { decimalComma }))
       .join(", ");
   }
-  // `sv-SE` is ISO-shaped — 2026-07-31, 2026-07-31 14:05:00 — which is both the
+  // `sv-SE` is ISO-shaped (2026-07-31, 2026-07-31 14:05:00), which is both the
   // Nordic form and the one Excel parses as a date rather than as text.
   if (value instanceof Date) {
     return Number.isNaN(value.getTime()) ? "" : value.toLocaleString("sv-SE");
@@ -90,7 +90,7 @@ export function formatExportValue(
 
 export 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;
@@ -100,7 +100,7 @@ export 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.
@@ -135,13 +135,13 @@ export function buildCellMatrix({
 }
 
 /**
- * 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.
  */
 export function buildGridCellMatrix<TData extends RowData>({
@@ -162,7 +162,7 @@ export function buildGridCellMatrix<TData extends RowData>({
     ...erased.getRightVisibleLeafColumns(),
   ];
   // The sorted model: after filtering, grouping and sorting, before expansion
-  // and paging — so a paged grid exports the whole filtered set, and a grouped
+  // and paging - so a paged grid exports the whole filtered set, and a grouped
   // grid exports the records under every group whether or not it is open.
   //
   // Walked by hand rather than taken from `flatRows`: in table-core
@@ -195,7 +195,7 @@ export function buildGridCellMatrix<TData extends RowData>({
 }
 
 /**
- * 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.
  *
@@ -243,7 +243,7 @@ function escapeField(value: string, separator: string): string {
  * 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.
  */
@@ -260,12 +260,12 @@ export 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.
  */
 export function toExcelCsv(
@@ -282,7 +282,7 @@ export function toExcelCsv(
  * 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.
  */
@@ -297,7 +297,7 @@ export async 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.
  */
 export function downloadTextFile({

package/src/tmdatagrid/core/cellNavigation.ts

@@ -4,7 +4,7 @@
  * 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
@@ -24,7 +24,7 @@ export type TMDataGridCellCoords = {
 export 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;
@@ -45,7 +45,7 @@ const clamp = (value: number, max: number) =>
  * 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
@@ -82,7 +82,7 @@ export function resolveCellMove({
       return at(from.rowIndex + Math.max(pageRows, 1), from.columnIndex);
     case "PageUp":
       return at(from.rowIndex - Math.max(pageRows, 1), from.columnIndex);
-    // Ctrl+Home / Ctrl+End address the grid, plain Home / End the row — the
+    // Ctrl+Home / Ctrl+End address the grid, plain Home / End the row - the
     // convention every spreadsheet and APG's own grid pattern share.
     case "Home":
       return ctrlKey ? at(0, 0) : at(from.rowIndex, 0);
@@ -104,13 +104,13 @@ export type NextEditableCellArgs = {
 };
 
 /**
- * The next editable cell in reading order, wrapping to the next row — and
+ * The next editable cell in reading order, wrapping to the next row - and
  * from the last cell of the grid back to the first. `null` when no other
  * cell is editable.
  *
  * Deliberately wrapping where {@link resolveCellMove} deliberately clamps:
  * arrows are a coordinate space and clamp so the destination is predictable,
- * but Tab mid-edit is the spreadsheet's "next field" — at the end of a row
+ * but Tab mid-edit is the spreadsheet's "next field" - at the end of a row
  * the next field is on the next row, which is a convention, not a surprise.
  */
 export function getNextEditableCell({

package/src/tmdatagrid/core/cellRange.ts

@@ -4,13 +4,13 @@ import type { TMDataGridCellPosition } from "./cellNavigation";
  * 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}.
  */
 export type TMDataGridCellRange = {
   anchor: TMDataGridCellPosition;
@@ -37,7 +37,7 @@ export 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.

package/src/tmdatagrid/core/columnOptions.ts

@@ -31,14 +31,14 @@ export type TMDataGridOptionsArgs = {
 };
 
 /**
- * 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) |
  */
 export type TMDataGridOptionsSource =
   | ReadonlyArray<TMDataGridOption | string>

package/src/tmdatagrid/core/columnOrdering.ts

@@ -12,7 +12,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.
  */
 export type TMDataGridColumnRegion = "left" | "center" | "right";
 
@@ -104,7 +104,7 @@ export 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.
  */
 export function getStepTargetColumn({

package/src/tmdatagrid/core/columnUtils.ts

@@ -34,7 +34,7 @@ export 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.
  */
 export function getColumnDefaultOperator(
@@ -51,13 +51,13 @@ export function getColumnAlign(column: ColumnLike): "left" | "right" | "center"
 }
 
 /**
- * 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