@ai-matrx/design-system 0.41.0 → 0.42.1

package/dist/{types-Dx5hJgCi.d.ts → types-afUz93xo.d.ts}

@@ -8,6 +8,7 @@ import { CellPatch } from './data-table/fill.js';
 import { ColumnFacets } from './data-table/facets.js';
 import { SpreadsheetIntent, SpreadsheetPastePlan } from './data-table/spreadsheet.js';
 import { DateColumnFilterValue } from './data-table/date-filter.js';
+import { MatrxTableMenuItem, MatrxTableMenuPayload, MatrxTableMenuSection } from './data-table/menu-targets.js';
 
 type TableSearchRole = "id" | "name" | "description" | "other";
 interface TableSearchScope {
@@ -147,6 +148,14 @@ interface MatrxColumnDef<T> {
      * again clears it.
      */
     filterSingle?: boolean;
+    /**
+     * THE CONSUMER'S OWN COLUMN ACTIONS, in the header's one menu — rename,
+     * insert left/right, use as the row label, colour by, settings — drawn under
+     * the built-in sort and filter, in the same popover, never a second control
+     * beside it. An item with `disabledReason` stays visible and says why it
+     * cannot run here. Absent or empty, the header menu is exactly what it was.
+     */
+    headerMenu?: MatrxTableMenuItem[];
     /** Allow an exact typed value not present in loaded select options. */
     filterAllowCustom?: boolean;
     /**
@@ -864,6 +873,16 @@ interface MatrxDataTableContextMenuConfig<T> {
         rowCount: number;
         columnIds: string[];
     }) => unknown;
+    /**
+     * NEUTRAL SECTIONS for whatever was right-clicked. Asked each time the menu
+     * opens, with the level's own payload — the cell's row, column and value; the
+     * row; the column's label and values; the selected range's ids and TSV; the
+     * table's row count — and answered with plain `MatrxTableMenuSection`s the
+     * host draws in its own right-click menu, beside what it already offers.
+     * Nothing here names a menu system. Absent, the right-click menu is exactly
+     * what it was.
+     */
+    sections?: (payload: MatrxTableMenuPayload<T>) => MatrxTableMenuSection[];
 }
 interface MatrxDataTableWindowConfig<T> {
     /** Window title. */
@@ -1177,7 +1196,20 @@ interface MatrxDataTableSpreadsheetConfig<T> {
      * clear, an undo and a redo. The table re-reads from `data`, so a write the
      * caller refuses simply never appears.
      */
-    onPatch: (patches: CellPatch[], intent: SpreadsheetIntent) => void | Promise<void>;
+    onPatch?: ((patches: CellPatch[], intent: SpreadsheetIntent) => void | Promise<void>) | undefined;
+    /**
+     * RANGE SELECTION AND COPY FOR A READER — a flag of its own, separate from
+     * editing. A person who may not change a table may still drag out a range,
+     * move it with the arrows, select all and press Cmd-C (or right-click the
+     * range) to take a real Excel/Sheets block out of it. With `readOnly` the
+     * grid offers every selection gesture and no write: no fill handle, no
+     * editor on Enter or typing, and cut, paste, clear, fill-down, undo and redo
+     * each say `readOnlyReason` rather than doing anything. `onPatch` is not
+     * needed. Default false.
+     */
+    readOnly?: boolean | undefined;
+    /** What a refused write says on a read-only grid. Defaults to a plain view-only sentence. */
+    readOnlyReason?: string | undefined;
     /** Column ids a patch may target. Defaults to every column marked `editable`. */
     writableColumnIds?: string[] | undefined;
     /** Why a column refuses a write, as a sentence a person can act on. */

package/dist/{types-DNkbHRVK.d.cts → types-q5ficDSo.d.cts}

@@ -8,6 +8,7 @@ import { CellPatch } from './data-table/fill.cjs';
 import { ColumnFacets } from './data-table/facets.cjs';
 import { SpreadsheetIntent, SpreadsheetPastePlan } from './data-table/spreadsheet.cjs';
 import { DateColumnFilterValue } from './data-table/date-filter.cjs';
+import { MatrxTableMenuItem, MatrxTableMenuPayload, MatrxTableMenuSection } from './data-table/menu-targets.cjs';
 
 type TableSearchRole = "id" | "name" | "description" | "other";
 interface TableSearchScope {
@@ -147,6 +148,14 @@ interface MatrxColumnDef<T> {
      * again clears it.
      */
     filterSingle?: boolean;
+    /**
+     * THE CONSUMER'S OWN COLUMN ACTIONS, in the header's one menu — rename,
+     * insert left/right, use as the row label, colour by, settings — drawn under
+     * the built-in sort and filter, in the same popover, never a second control
+     * beside it. An item with `disabledReason` stays visible and says why it
+     * cannot run here. Absent or empty, the header menu is exactly what it was.
+     */
+    headerMenu?: MatrxTableMenuItem[];
     /** Allow an exact typed value not present in loaded select options. */
     filterAllowCustom?: boolean;
     /**
@@ -864,6 +873,16 @@ interface MatrxDataTableContextMenuConfig<T> {
         rowCount: number;
         columnIds: string[];
     }) => unknown;
+    /**
+     * NEUTRAL SECTIONS for whatever was right-clicked. Asked each time the menu
+     * opens, with the level's own payload — the cell's row, column and value; the
+     * row; the column's label and values; the selected range's ids and TSV; the
+     * table's row count — and answered with plain `MatrxTableMenuSection`s the
+     * host draws in its own right-click menu, beside what it already offers.
+     * Nothing here names a menu system. Absent, the right-click menu is exactly
+     * what it was.
+     */
+    sections?: (payload: MatrxTableMenuPayload<T>) => MatrxTableMenuSection[];
 }
 interface MatrxDataTableWindowConfig<T> {
     /** Window title. */
@@ -1177,7 +1196,20 @@ interface MatrxDataTableSpreadsheetConfig<T> {
      * clear, an undo and a redo. The table re-reads from `data`, so a write the
      * caller refuses simply never appears.
      */
-    onPatch: (patches: CellPatch[], intent: SpreadsheetIntent) => void | Promise<void>;
+    onPatch?: ((patches: CellPatch[], intent: SpreadsheetIntent) => void | Promise<void>) | undefined;
+    /**
+     * RANGE SELECTION AND COPY FOR A READER — a flag of its own, separate from
+     * editing. A person who may not change a table may still drag out a range,
+     * move it with the arrows, select all and press Cmd-C (or right-click the
+     * range) to take a real Excel/Sheets block out of it. With `readOnly` the
+     * grid offers every selection gesture and no write: no fill handle, no
+     * editor on Enter or typing, and cut, paste, clear, fill-down, undo and redo
+     * each say `readOnlyReason` rather than doing anything. `onPatch` is not
+     * needed. Default false.
+     */
+    readOnly?: boolean | undefined;
+    /** What a refused write says on a read-only grid. Defaults to a plain view-only sentence. */
+    readOnlyReason?: string | undefined;
     /** Column ids a patch may target. Defaults to every column marked `editable`. */
     writableColumnIds?: string[] | undefined;
     /** Why a column refuses a write, as a sentence a person can act on. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-matrx/design-system",
-  "version": "0.41.0",
+  "version": "0.42.1",
   "description": "AI Matrx semantic React primitives shared across Vite, Next.js, desktop, and customer-built applications.",
   "type": "module",
   "license": "MIT",