eidos-ui 1.2.0 → 2.1.0

package/dist/Avatar.types-BY-C09Ke.d.cts

@@ -0,0 +1,23 @@
+import React__default from 'react';
+
+type AvatarSize = 'sm' | 'md' | 'lg';
+type AvatarColor = 'primary' | 'secondary' | 'success' | 'danger' | 'warning' | 'info' | 'gray';
+interface AvatarProps {
+    src?: string;
+    alt?: string;
+    name?: string;
+    size?: AvatarSize;
+    color?: AvatarColor;
+    shape?: 'circle' | 'square';
+    fallback?: React__default.ReactNode;
+    className?: string;
+    onClick?: () => void;
+}
+interface AvatarGroupProps {
+    children: React__default.ReactNode;
+    max?: number;
+    size?: AvatarSize;
+    className?: string;
+}
+
+export type { AvatarColor as A, AvatarGroupProps as a, AvatarProps as b, AvatarSize as c };

package/dist/Avatar.types-BY-C09Ke.d.ts

@@ -0,0 +1,23 @@
+import React__default from 'react';
+
+type AvatarSize = 'sm' | 'md' | 'lg';
+type AvatarColor = 'primary' | 'secondary' | 'success' | 'danger' | 'warning' | 'info' | 'gray';
+interface AvatarProps {
+    src?: string;
+    alt?: string;
+    name?: string;
+    size?: AvatarSize;
+    color?: AvatarColor;
+    shape?: 'circle' | 'square';
+    fallback?: React__default.ReactNode;
+    className?: string;
+    onClick?: () => void;
+}
+interface AvatarGroupProps {
+    children: React__default.ReactNode;
+    max?: number;
+    size?: AvatarSize;
+    className?: string;
+}
+
+export type { AvatarColor as A, AvatarGroupProps as a, AvatarProps as b, AvatarSize as c };

package/dist/{Header.types-BZi80bWz.d.cts → Header.types-B3QtuiL-.d.cts}

@@ -1,10 +1,14 @@
 import { T as TextButtonProps, I as IconButtonProps } from './Button.types-DZRCVqyN.cjs';
 
 interface HeaderProps {
-    /** Page or section title. */
-    title: string;
+    /**
+     * Page or section title. Accepts inline nodes alongside the text - a
+     * status `Pill`/`Chip` beside the title is the common case - not just a
+     * string. Keep the children inline-level; the title is a heading.
+     */
+    title: React.ReactNode;
     /** Supporting text rendered below the title. */
-    subtitle?: string | React.ReactNode;
+    subtitle?: React.ReactNode;
     /** Trailing action buttons, rendered right-aligned. */
     actions?: HeaderActionProps[];
     className?: string;

package/dist/{Header.types-DJt-q01P.d.ts → Header.types-C6w0FBY8.d.ts}

@@ -1,10 +1,14 @@
 import { T as TextButtonProps, I as IconButtonProps } from './Button.types-BH0CPyPx.js';
 
 interface HeaderProps {
-    /** Page or section title. */
-    title: string;
+    /**
+     * Page or section title. Accepts inline nodes alongside the text - a
+     * status `Pill`/`Chip` beside the title is the common case - not just a
+     * string. Keep the children inline-level; the title is a heading.
+     */
+    title: React.ReactNode;
     /** Supporting text rendered below the title. */
-    subtitle?: string | React.ReactNode;
+    subtitle?: React.ReactNode;
     /** Trailing action buttons, rendered right-aligned. */
     actions?: HeaderActionProps[];
     className?: string;

package/dist/Table.types-CPj-udMc.d.cts

@@ -0,0 +1,278 @@
+import { ReactNode } from 'react';
+import { I as IconType } from './renderIcon-C2lEMMzb.cjs';
+import { B as ButtonColorProps, b as ButtonVariantProps } from './Button.types-DZRCVqyN.cjs';
+
+/**
+ * A field name of a row-data type, as a string-literal union.
+ *
+ * Shared by every data component that addresses row fields by name
+ * (`Table`, `DataGrid`) so the same concept is typed one way everywhere -
+ * `TableColumn.key`, `DataGridColumn.key`, `rowKey`, sort keys, and the
+ * filter/quick-filter schemas.
+ *
+ * Degrades to `string` for the untyped default (`Record<string, unknown>`),
+ * which is what keeps callers who never specify `T` compiling unchanged.
+ *
+ * `Extract<keyof T, string>` rather than `keyof T`: keys are compared against
+ * and rendered as strings throughout (`data-col-key`, React keys, filter
+ * state objects), so numeric and symbol keys are excluded deliberately.
+ *
+ * ## Why this only works when `T` has no index signature
+ *
+ * An index signature widens `keyof T` to `string`, at which point this
+ * resolves to `string` and every key-narrowing and per-key value type built
+ * on it silently degrades to the old, unchecked behaviour. That is exactly
+ * what `T extends Record<string, unknown>` used to force on consumers:
+ * TypeScript only grants *implicit* index signatures to object type aliases,
+ * so anyone modelling rows with an `interface` had to write
+ * `interface Row extends Record<string, unknown>` to satisfy it - and thereby
+ * opted out of all of this without knowing.
+ *
+ * Both components now constrain `T extends object` instead, so a plain
+ * interface is accepted and keeps its literal keys. Don't tighten that
+ * constraint back to `Record<string, unknown>`: it would not fail loudly, it
+ * would just quietly stop checking.
+ */
+type RowKey<T> = Extract<keyof T, string>;
+
+/** A secondary action inside a `type: 'split-button'` bulk action's dropdown. */
+interface BulkActionSplitOption<T> {
+    id: string;
+    label: string;
+    icon?: IconType;
+    disabled?: boolean;
+    /** Receives the full array of currently selected row objects. */
+    onClick: (selectedRows: T[]) => void;
+}
+interface BulkActionCommon<T> {
+    /** Only needs to be unique within this `bulkActions` array. */
+    id: string;
+    color?: ButtonColorProps;
+    disabled?: boolean | ((selectedRows: T[]) => boolean);
+    /** Primary action - fired on click for `'button'`, or on the primary (left) segment for `'split-button'`. */
+    onClick: (selectedRows: T[]) => void;
+}
+interface BulkActionButton<T> extends BulkActionCommon<T> {
+    /** @default 'button' */
+    type?: 'button';
+    /** Omit to render an icon-only button - `icon` becomes the sole icon in that case. */
+    label?: string;
+    icon?: IconType;
+    posIcon?: IconType;
+    variant?: ButtonVariantProps;
+}
+interface BulkActionSplitButton<T> extends BulkActionCommon<T> {
+    type: 'split-button';
+    /** Required - SplitButton always renders a primary label. */
+    label: string;
+    icon?: IconType;
+    /** SplitButton has no `text` variant. */
+    variant?: Exclude<ButtonVariantProps, 'text'>;
+    /** Secondary actions shown in the split-button's dropdown. */
+    options: BulkActionSplitOption<T>[];
+}
+type BulkAction<T> = BulkActionButton<T> | BulkActionSplitButton<T>;
+/** Members shared by every column variant, field-addressing or not. */
+interface TableColumnCommon {
+    label: string;
+    sortable?: boolean;
+    filterable?: boolean;
+    filterType?: 'text' | 'select' | 'date' | 'boolean';
+    filterOptions?: {
+        id: string;
+        value: string;
+        label: string;
+    }[];
+    dateFilterMode?: 'single' | 'multiple' | 'range';
+    width?: string;
+    /**
+     * Cell text alignment. Applies in table mode only: card view renders each
+     * field as a label above its value, where aligning the value away from its
+     * own label reads as a misalignment rather than a choice.
+     *
+     * Ignored on `type: 'icon'` and `type: 'action'` columns, which are always
+     * centred - they hold a single control in a fixed-width cell, so there is
+     * nothing to align it within. `DataGrid`'s actions column behaves the same.
+     */
+    align?: 'left' | 'center' | 'right';
+    /** Enables position:sticky on this column */
+    pin?: 'left' | 'right';
+    /**
+     * Render this column's value as the card's title instead of a label:value
+     * field row. Only the first column with `cardHeader` set is used - if
+     * several are marked, the rest render as normal fields.
+     */
+    cardHeader?: boolean;
+    /**
+     * Render this column's value as the card's subtitle, directly under the
+     * `cardHeader` value. Only the first column with `cardSubheader` set is
+     * used. Has no effect without a `cardHeader` column also being set.
+     */
+    cardSubheader?: boolean;
+}
+/**
+ * A column bound to the row field named by `key`, which is what lets `render`
+ * receive `T[K]` rather than `unknown`.
+ *
+ * Not used directly - `TableColumn` distributes this over `keyof T` so each
+ * entry correlates its own `key` with its own value type.
+ */
+interface TableValueColumn<T extends object, K extends RowKey<T>> extends TableColumnCommon {
+    key: K;
+    /** @default 'data' */
+    type?: 'data';
+    render?: (value: T[K], item: T) => ReactNode;
+}
+/**
+ * A column that renders from the whole row rather than one field - an icon or
+ * action cell, or a computed/composite value. `key` is free-form here because
+ * nothing reads `row[key]`: it's only an identity for React keys, sorting and
+ * `data-col-key`.
+ *
+ * `'icon'` and `'action'` carry their existing cell styling; `'custom'` styles
+ * like a normal data cell but takes a free-form key, which is the home for a
+ * derived column (previously expressible only by pointing `key` at a field
+ * that didn't exist).
+ */
+interface TableCustomColumn<T extends object> extends TableColumnCommon {
+    /** Free-form - must only be unique within `columns`. */
+    key: string;
+    type: 'icon' | 'action' | 'custom';
+    /** `value` is always `undefined`; render from `item`. */
+    render?: (value: undefined, item: T) => ReactNode;
+}
+/**
+ * One column definition. A union of two variants, discriminated on `type`:
+ *
+ * - **value column** (default, `type` omitted or `'data'`) - `key` must be a
+ *   field of `T`, and `render` receives that field's type instead of `unknown`.
+ * - **`type: 'icon' | 'action' | 'custom'`** - renders from the whole row;
+ *   `key` is free-form.
+ *
+ * With the untyped default `T`, `RowKey<T>` is `string` and `T[K]` is
+ * `unknown`, which is byte-identical to the pre-2.0 behaviour.
+ *
+ * Replaces `key: keyof T | string`, which looked constrained but wasn't:
+ * `keyof T` is assignable to `string`, so that union collapsed to plain
+ * `string` and checked nothing.
+ */
+type TableColumn<T extends object = Record<string, unknown>> = {
+    [K in RowKey<T>]: TableValueColumn<T, K>;
+}[RowKey<T>] | TableCustomColumn<T>;
+type FilterValue = string | string[] | boolean | {
+    start: string | null;
+    end: string | null;
+} | undefined;
+interface TableFilters {
+    [key: string]: FilterValue;
+}
+interface TableProps<T extends object = Record<string, unknown>> {
+    data: T[];
+    columns: TableColumn<T>[];
+    loading?: boolean;
+    emptyMessage?: string;
+    onRowClick?: (item: T) => void;
+    className?: string;
+    showFooter?: boolean;
+    totalItems?: number;
+    showPagination?: boolean;
+    pageSize?: number;
+    pageSizeOptions?: number[];
+    onSortChange?: (sortBy: RowKey<T>, sortDirection: 'asc' | 'desc') => void;
+    currentSort?: {
+        key: RowKey<T>;
+        direction: 'asc' | 'desc';
+    };
+    filters?: TableFilters;
+    onFiltersChange?: (filters: TableFilters) => void;
+    defaultFilters?: TableFilters;
+    showFilters?: boolean;
+    selectable?: boolean;
+    rowKey?: RowKey<T>;
+    selectedRows?: string[];
+    defaultSelectedRows?: string[];
+    /**
+     * Fires with every selected key, plus the row object for each of those keys.
+     *
+     * `selectedKeys` is authoritative; `selectedRows` is best-effort. The row
+     * for each selected key is cached, so a row selected while it was rendered
+     * still comes back after `data` has moved on - but a key that was selected
+     * before the table ever saw its row (seeded via `defaultSelectedRows`, say)
+     * has no row to hand back.
+     */
+    onSelectionChange?: (selectedKeys: string[], selectedRows: T[]) => void;
+    /**
+     * What the select-all control acts on - the header checkbox in table mode,
+     * or the toolbar checkbox in card view (where there is no header row):
+     *
+     * - `'all'` - every row in `data`, across pages.
+     * - `'page'` - only the rows currently rendered.
+     *
+     * Either way it only ever adds to or removes from the rows in its own
+     * scope, so a selection made on another page survives.
+     *
+     * `'all'` can only reach the rows the table actually holds: if `data` is one
+     * page of a larger set (with `totalItems` describing the whole), it cannot
+     * know the keys of rows it has never received, and says so with a dev-only
+     * warning. Matches `DataGrid.selectAllScope`.
+     *
+     * @default 'all'
+     */
+    selectAllScope?: 'all' | 'page';
+    /**
+     * Resolves the keys of **every** row matching the current query, including
+     * rows not present in `data`. Supplying it adds a "Select all N" action to
+     * the toolbar once everything the table does hold is selected.
+     *
+     * Only relevant when `data` is a subset of a larger set and `totalItems`
+     * describes the whole - a table paginating its own `data` already has every
+     * key. Called with no arguments, may be async (the action shows a loading
+     * state), and whatever it returns replaces the selection.
+     *
+     * Matches `DataGrid.onSelectAllMatching`, which is where this mostly earns
+     * its keep: `DataGrid` has a real server-side pagination mode.
+     */
+    onSelectAllMatching?: () => string[] | Promise<string[]>;
+    bulkActions?: BulkAction<T>[];
+    density?: 'compact' | 'comfortable' | 'spacious';
+    showColumnVisibility?: boolean;
+    showExport?: boolean;
+    showDensity?: boolean;
+    draggableColumns?: boolean;
+    onColumnReorder?: (newColumns: TableColumn<T>[]) => void;
+    /**
+     * On by default: below `cardViewBreakpoint`, or once the table's own width
+     * can no longer fit every visible column at a usable width, swap the table
+     * for a stacked list of cards - one per row. Only the row rendering
+     * changes; the toolbar, pagination, filtering, sorting and selection all
+     * keep working. `draggableColumns` has no effect in card view (there are no
+     * column headers to drag).
+     *
+     * Matches `DataGridProps.hasCardView` - both components use the same
+     * defaults and the same measured-container logic. Set to `false` to always
+     * render a table.
+     *
+     * @default true
+     */
+    hasCardView?: boolean;
+    /**
+     * Container width (px) at/below which card view kicks in. This is an
+     * explicit floor - card view also switches on automatically, regardless
+     * of this value, once the container can't fit every visible column at a
+     * usable minimum width, so a many-column table never has to overflow
+     * horizontally waiting for a hand-tuned breakpoint.
+     *
+     * @default 640
+     */
+    cardViewBreakpoint?: number;
+    /**
+     * Cards lay out in a responsive grid (CSS `repeat(auto-fill, minmax(...))`)
+     * rather than one per row - this sets the minimum width (px) a card can
+     * shrink to before the next one wraps to a new row.
+     *
+     * @default 280
+     */
+    cardMinWidth?: number;
+}
+
+export type { BulkAction as B, FilterValue as F, RowKey as R, TableColumn as T, BulkActionButton as a, BulkActionSplitButton as b, BulkActionSplitOption as c, TableCustomColumn as d, TableFilters as e, TableProps as f, TableValueColumn as g };

package/dist/Table.types-CZZ7QWAI.d.ts

@@ -0,0 +1,278 @@
+import { ReactNode } from 'react';
+import { I as IconType } from './renderIcon-C2lEMMzb.js';
+import { B as ButtonColorProps, b as ButtonVariantProps } from './Button.types-BH0CPyPx.js';
+
+/**
+ * A field name of a row-data type, as a string-literal union.
+ *
+ * Shared by every data component that addresses row fields by name
+ * (`Table`, `DataGrid`) so the same concept is typed one way everywhere -
+ * `TableColumn.key`, `DataGridColumn.key`, `rowKey`, sort keys, and the
+ * filter/quick-filter schemas.
+ *
+ * Degrades to `string` for the untyped default (`Record<string, unknown>`),
+ * which is what keeps callers who never specify `T` compiling unchanged.
+ *
+ * `Extract<keyof T, string>` rather than `keyof T`: keys are compared against
+ * and rendered as strings throughout (`data-col-key`, React keys, filter
+ * state objects), so numeric and symbol keys are excluded deliberately.
+ *
+ * ## Why this only works when `T` has no index signature
+ *
+ * An index signature widens `keyof T` to `string`, at which point this
+ * resolves to `string` and every key-narrowing and per-key value type built
+ * on it silently degrades to the old, unchecked behaviour. That is exactly
+ * what `T extends Record<string, unknown>` used to force on consumers:
+ * TypeScript only grants *implicit* index signatures to object type aliases,
+ * so anyone modelling rows with an `interface` had to write
+ * `interface Row extends Record<string, unknown>` to satisfy it - and thereby
+ * opted out of all of this without knowing.
+ *
+ * Both components now constrain `T extends object` instead, so a plain
+ * interface is accepted and keeps its literal keys. Don't tighten that
+ * constraint back to `Record<string, unknown>`: it would not fail loudly, it
+ * would just quietly stop checking.
+ */
+type RowKey<T> = Extract<keyof T, string>;
+
+/** A secondary action inside a `type: 'split-button'` bulk action's dropdown. */
+interface BulkActionSplitOption<T> {
+    id: string;
+    label: string;
+    icon?: IconType;
+    disabled?: boolean;
+    /** Receives the full array of currently selected row objects. */
+    onClick: (selectedRows: T[]) => void;
+}
+interface BulkActionCommon<T> {
+    /** Only needs to be unique within this `bulkActions` array. */
+    id: string;
+    color?: ButtonColorProps;
+    disabled?: boolean | ((selectedRows: T[]) => boolean);
+    /** Primary action - fired on click for `'button'`, or on the primary (left) segment for `'split-button'`. */
+    onClick: (selectedRows: T[]) => void;
+}
+interface BulkActionButton<T> extends BulkActionCommon<T> {
+    /** @default 'button' */
+    type?: 'button';
+    /** Omit to render an icon-only button - `icon` becomes the sole icon in that case. */
+    label?: string;
+    icon?: IconType;
+    posIcon?: IconType;
+    variant?: ButtonVariantProps;
+}
+interface BulkActionSplitButton<T> extends BulkActionCommon<T> {
+    type: 'split-button';
+    /** Required - SplitButton always renders a primary label. */
+    label: string;
+    icon?: IconType;
+    /** SplitButton has no `text` variant. */
+    variant?: Exclude<ButtonVariantProps, 'text'>;
+    /** Secondary actions shown in the split-button's dropdown. */
+    options: BulkActionSplitOption<T>[];
+}
+type BulkAction<T> = BulkActionButton<T> | BulkActionSplitButton<T>;
+/** Members shared by every column variant, field-addressing or not. */
+interface TableColumnCommon {
+    label: string;
+    sortable?: boolean;
+    filterable?: boolean;
+    filterType?: 'text' | 'select' | 'date' | 'boolean';
+    filterOptions?: {
+        id: string;
+        value: string;
+        label: string;
+    }[];
+    dateFilterMode?: 'single' | 'multiple' | 'range';
+    width?: string;
+    /**
+     * Cell text alignment. Applies in table mode only: card view renders each
+     * field as a label above its value, where aligning the value away from its
+     * own label reads as a misalignment rather than a choice.
+     *
+     * Ignored on `type: 'icon'` and `type: 'action'` columns, which are always
+     * centred - they hold a single control in a fixed-width cell, so there is
+     * nothing to align it within. `DataGrid`'s actions column behaves the same.
+     */
+    align?: 'left' | 'center' | 'right';
+    /** Enables position:sticky on this column */
+    pin?: 'left' | 'right';
+    /**
+     * Render this column's value as the card's title instead of a label:value
+     * field row. Only the first column with `cardHeader` set is used - if
+     * several are marked, the rest render as normal fields.
+     */
+    cardHeader?: boolean;
+    /**
+     * Render this column's value as the card's subtitle, directly under the
+     * `cardHeader` value. Only the first column with `cardSubheader` set is
+     * used. Has no effect without a `cardHeader` column also being set.
+     */
+    cardSubheader?: boolean;
+}
+/**
+ * A column bound to the row field named by `key`, which is what lets `render`
+ * receive `T[K]` rather than `unknown`.
+ *
+ * Not used directly - `TableColumn` distributes this over `keyof T` so each
+ * entry correlates its own `key` with its own value type.
+ */
+interface TableValueColumn<T extends object, K extends RowKey<T>> extends TableColumnCommon {
+    key: K;
+    /** @default 'data' */
+    type?: 'data';
+    render?: (value: T[K], item: T) => ReactNode;
+}
+/**
+ * A column that renders from the whole row rather than one field - an icon or
+ * action cell, or a computed/composite value. `key` is free-form here because
+ * nothing reads `row[key]`: it's only an identity for React keys, sorting and
+ * `data-col-key`.
+ *
+ * `'icon'` and `'action'` carry their existing cell styling; `'custom'` styles
+ * like a normal data cell but takes a free-form key, which is the home for a
+ * derived column (previously expressible only by pointing `key` at a field
+ * that didn't exist).
+ */
+interface TableCustomColumn<T extends object> extends TableColumnCommon {
+    /** Free-form - must only be unique within `columns`. */
+    key: string;
+    type: 'icon' | 'action' | 'custom';
+    /** `value` is always `undefined`; render from `item`. */
+    render?: (value: undefined, item: T) => ReactNode;
+}
+/**
+ * One column definition. A union of two variants, discriminated on `type`:
+ *
+ * - **value column** (default, `type` omitted or `'data'`) - `key` must be a
+ *   field of `T`, and `render` receives that field's type instead of `unknown`.
+ * - **`type: 'icon' | 'action' | 'custom'`** - renders from the whole row;
+ *   `key` is free-form.
+ *
+ * With the untyped default `T`, `RowKey<T>` is `string` and `T[K]` is
+ * `unknown`, which is byte-identical to the pre-2.0 behaviour.
+ *
+ * Replaces `key: keyof T | string`, which looked constrained but wasn't:
+ * `keyof T` is assignable to `string`, so that union collapsed to plain
+ * `string` and checked nothing.
+ */
+type TableColumn<T extends object = Record<string, unknown>> = {
+    [K in RowKey<T>]: TableValueColumn<T, K>;
+}[RowKey<T>] | TableCustomColumn<T>;
+type FilterValue = string | string[] | boolean | {
+    start: string | null;
+    end: string | null;
+} | undefined;
+interface TableFilters {
+    [key: string]: FilterValue;
+}
+interface TableProps<T extends object = Record<string, unknown>> {
+    data: T[];
+    columns: TableColumn<T>[];
+    loading?: boolean;
+    emptyMessage?: string;
+    onRowClick?: (item: T) => void;
+    className?: string;
+    showFooter?: boolean;
+    totalItems?: number;
+    showPagination?: boolean;
+    pageSize?: number;
+    pageSizeOptions?: number[];
+    onSortChange?: (sortBy: RowKey<T>, sortDirection: 'asc' | 'desc') => void;
+    currentSort?: {
+        key: RowKey<T>;
+        direction: 'asc' | 'desc';
+    };
+    filters?: TableFilters;
+    onFiltersChange?: (filters: TableFilters) => void;
+    defaultFilters?: TableFilters;
+    showFilters?: boolean;
+    selectable?: boolean;
+    rowKey?: RowKey<T>;
+    selectedRows?: string[];
+    defaultSelectedRows?: string[];
+    /**
+     * Fires with every selected key, plus the row object for each of those keys.
+     *
+     * `selectedKeys` is authoritative; `selectedRows` is best-effort. The row
+     * for each selected key is cached, so a row selected while it was rendered
+     * still comes back after `data` has moved on - but a key that was selected
+     * before the table ever saw its row (seeded via `defaultSelectedRows`, say)
+     * has no row to hand back.
+     */
+    onSelectionChange?: (selectedKeys: string[], selectedRows: T[]) => void;
+    /**
+     * What the select-all control acts on - the header checkbox in table mode,
+     * or the toolbar checkbox in card view (where there is no header row):
+     *
+     * - `'all'` - every row in `data`, across pages.
+     * - `'page'` - only the rows currently rendered.
+     *
+     * Either way it only ever adds to or removes from the rows in its own
+     * scope, so a selection made on another page survives.
+     *
+     * `'all'` can only reach the rows the table actually holds: if `data` is one
+     * page of a larger set (with `totalItems` describing the whole), it cannot
+     * know the keys of rows it has never received, and says so with a dev-only
+     * warning. Matches `DataGrid.selectAllScope`.
+     *
+     * @default 'all'
+     */
+    selectAllScope?: 'all' | 'page';
+    /**
+     * Resolves the keys of **every** row matching the current query, including
+     * rows not present in `data`. Supplying it adds a "Select all N" action to
+     * the toolbar once everything the table does hold is selected.
+     *
+     * Only relevant when `data` is a subset of a larger set and `totalItems`
+     * describes the whole - a table paginating its own `data` already has every
+     * key. Called with no arguments, may be async (the action shows a loading
+     * state), and whatever it returns replaces the selection.
+     *
+     * Matches `DataGrid.onSelectAllMatching`, which is where this mostly earns
+     * its keep: `DataGrid` has a real server-side pagination mode.
+     */
+    onSelectAllMatching?: () => string[] | Promise<string[]>;
+    bulkActions?: BulkAction<T>[];
+    density?: 'compact' | 'comfortable' | 'spacious';
+    showColumnVisibility?: boolean;
+    showExport?: boolean;
+    showDensity?: boolean;
+    draggableColumns?: boolean;
+    onColumnReorder?: (newColumns: TableColumn<T>[]) => void;
+    /**
+     * On by default: below `cardViewBreakpoint`, or once the table's own width
+     * can no longer fit every visible column at a usable width, swap the table
+     * for a stacked list of cards - one per row. Only the row rendering
+     * changes; the toolbar, pagination, filtering, sorting and selection all
+     * keep working. `draggableColumns` has no effect in card view (there are no
+     * column headers to drag).
+     *
+     * Matches `DataGridProps.hasCardView` - both components use the same
+     * defaults and the same measured-container logic. Set to `false` to always
+     * render a table.
+     *
+     * @default true
+     */
+    hasCardView?: boolean;
+    /**
+     * Container width (px) at/below which card view kicks in. This is an
+     * explicit floor - card view also switches on automatically, regardless
+     * of this value, once the container can't fit every visible column at a
+     * usable minimum width, so a many-column table never has to overflow
+     * horizontally waiting for a hand-tuned breakpoint.
+     *
+     * @default 640
+     */
+    cardViewBreakpoint?: number;
+    /**
+     * Cards lay out in a responsive grid (CSS `repeat(auto-fill, minmax(...))`)
+     * rather than one per row - this sets the minimum width (px) a card can
+     * shrink to before the next one wraps to a new row.
+     *
+     * @default 280
+     */
+    cardMinWidth?: number;
+}
+
+export type { BulkAction as B, FilterValue as F, RowKey as R, TableColumn as T, BulkActionButton as a, BulkActionSplitButton as b, BulkActionSplitOption as c, TableCustomColumn as d, TableFilters as e, TableProps as f, TableValueColumn as g };

package/dist/Toolbar.types-DSk8z2iy.d.cts

@@ -0,0 +1,38 @@
+import { a as BreadcrumbProps } from './Breadcrumb.types-DaykU-C8.cjs';
+import { b as AvatarProps } from './Avatar.types-BY-C09Ke.cjs';
+import { I as IconButtonProps } from './Button.types-DZRCVqyN.cjs';
+import { b as MenuItemType } from './Menu.types-DwcuCZM7.cjs';
+import { C as CommandItem } from './CommandPalette.types-DRMMS_ev.cjs';
+
+interface ToolbarProps {
+    /** Breadcrumb trail rendered above the page. Omit to leave the leading region empty. */
+    breadcrumbs?: Pick<BreadcrumbProps, 'items' | 'separator'>;
+    /**
+     * The signed-in user, rendered as the `Avatar` at the far right. Omit it
+     * (along with `userMenu`) to render no avatar at all.
+     */
+    user?: Pick<AvatarProps, 'name' | 'src' | 'color'>;
+    /**
+     * User menu items, opened from the `user` avatar. Omit (or pass an empty
+     * array) to render the avatar as a plain, non-interactive mark.
+     */
+    userMenu?: MenuItemType[];
+    /** Command palette items, rendered right-aligned. */
+    cmdPaletteItems?: CommandItem[];
+    /**
+     * Free-form content rendered at the start of the trailing region, before
+     * the command palette trigger - an environment badge, an org/tenant
+     * switcher, a global toggle. Unlike `actions`, which is a restricted
+     * button subset, this region takes any node and is laid out as-is.
+     */
+    content?: React.ReactNode;
+    /** Trailing action buttons, rendered right-aligned. */
+    actions?: ToolbarActionProps[];
+    className?: string;
+}
+/**
+ * Restricted, discriminated subset of ButtonProps for Toolbar actions.
+ */
+type ToolbarActionProps = Pick<IconButtonProps, 'color' | 'loading' | 'disabled' | 'preIcon' | 'posIcon' | 'icon' | 'children' | 'onClick' | 'tooltip'>;
+
+export type { ToolbarActionProps as T, ToolbarProps as a };