@12-apps/ui 5.0.0 → 5.0.1

package/dist/types/components/data-display/DataViews/data-views-drag.d.ts

@@ -0,0 +1,117 @@
+import { type ReactNode } from "react";
+/**
+ * DRAGGING, OWNED BY THE CONTAINER AND NOT BY THE CARD.
+ *
+ * A card cannot know whether it is draggable. The same `BaseListCard` renders
+ * inside a reorderable queue, a read-only report and a board column that moves
+ * items between columns — and only the thing holding them knows which. So the
+ * container publishes a drag context and every card inside it becomes
+ * draggable; a card with no container above it renders exactly as before, with
+ * no handle and no listeners.
+ *
+ * This is a SEAM, not a drag implementation. It carries whatever props the
+ * host's library hands out — dnd-kit's `attributes`/`listeners`, react-dnd's
+ * connector output, or plain HTML5 `draggable` + `onDragStart` — because
+ * picking one of those for every consumer of `@12-apps/ui` is a decision this
+ * package has no business making. There is no drag dependency here, and adding
+ * one would force it on every app that installs the library.
+ */
+/** The props a container hands to one item. Deliberately untyped-ish: each DnD library has its own shape. */
+export type DragItemProps = Record<string, unknown>;
+export interface DragContainerValue {
+    /**
+     * Props for the item's ROOT — the element that moves. dnd-kit wants its
+     * `setNodeRef` and transform style here; HTML5 wants `draggable` and
+     * `onDragStart`.
+     */
+    itemProps: (id: string | number) => DragItemProps;
+    /**
+     * Props for the HANDLE alone, when the container wants drags to start only
+     * from the grip.
+     *
+     * Whole-card dragging breaks the two things a card must still do: selecting
+     * text in it, and hitting the checkbox without the row sliding away. When a
+     * container returns handle props, the card puts them on the grip and leaves
+     * the rest of itself alone.
+     */
+    handleProps?: (id: string | number) => DragItemProps;
+    /** The id currently being dragged, so its card can dim itself. */
+    activeId?: string | number | null;
+    /**
+     * WHERE THE DRAGGED ITEM WOULD LAND — the one thing a drag cannot be honest
+     * without.
+     *
+     * A list that dims the row you picked up and shows nothing else asks you to
+     * guess the outcome and find out by dropping. The marker turns that into a
+     * statement: THIS gap is where it goes.
+     *
+     * Published by the container, not computed by the card, for the same reason
+     * everything else here is: only the thing holding the items knows the
+     * geometry — which one you are over, which edge of it, and whether that
+     * position is legal. A card knows none of that about its neighbours.
+     *
+     * `null` while nothing is being dragged, or while the pointer is over no
+     * valid target.
+     */
+    dropIndicator?: {
+        id: string | number;
+        edge: "before" | "after";
+    } | null;
+}
+/**
+ * Marks everything inside as draggable. Cards read this; nothing else does.
+ */
+export declare function DragContainerProvider({ value, children, }: {
+    value: DragContainerValue;
+    children: ReactNode;
+}): React.JSX.Element;
+/**
+ * What one card needs to know about dragging.
+ *
+ * Returns the inert answer when there is no container OR no `dragId` — a card
+ * that forgot its id must not render a handle that does nothing, which is worse
+ * than no handle at all.
+ */
+export declare function useDragItem(dragId: string | number | undefined): {
+    draggable: boolean;
+    itemProps: DragItemProps;
+    handleProps: DragItemProps | undefined;
+    dragging: boolean;
+    /** Which of this card's edges the marker sits on, or null for neither. */
+    dropEdge: "before" | "after" | null;
+};
+/**
+ * THE DROP MARKER — one rule across the card's edge, drawn where the item lands.
+ *
+ * Shared by every draggable surface rather than reimplemented per card, so a
+ * reorderable list, a board column and a grid of tiles all say the same thing
+ * the same way. A consumer wiring its own DnD gets this for free by publishing
+ * `dropIndicator`; it never draws the marker itself.
+ *
+ * ABSOLUTE, AND OUTSIDE THE FLOW ON PURPOSE. A marker that took layout space
+ * would push every row below it down by its own height the moment it appeared —
+ * the list would twitch as you dragged across it, and the gap you were aiming
+ * at would move out from under the pointer. Drawn over the gap instead, nothing
+ * reflows.
+ *
+ * `pointerEvents: none` so it cannot swallow the dragover events that placed it,
+ * and `aria-hidden` because the position it reports belongs in a live region the
+ * LIST owns — fifty rows each announcing a marker is a screen-reader nightmare.
+ */
+export declare function DropIndicator({ edge }: {
+    edge: "before" | "after";
+}): React.JSX.Element;
+/**
+ * The grip. Six dots, the convention everywhere, drawn rather than imported so
+ * this costs no icon dependency.
+ *
+ * `cursor: grab` on the handle only when the container gates drags to it —
+ * otherwise the whole card carries the cursor and the handle is just an
+ * affordance saying so.
+ */
+export declare function DragHandle({ handleProps, gated, testId, }: {
+    handleProps: DragItemProps | undefined;
+    gated: boolean;
+    testId?: string;
+}): React.JSX.Element;
+//# sourceMappingURL=data-views-drag.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-drag.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-drag.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-drag.tsx"],"names":[],"mappings":"AAEA,OAAO,EAA6B,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAIlE;;;;;;;;;;;;;;;;GAgBG;AAEH,6GAA6G;AAC7G,MAAM,MAAM,aAAa,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AAEpD,MAAM,WAAW,kBAAkB;IACjC;;;;OAIG;IACH,SAAS,EAAE,CAAC,EAAE,EAAE,MAAM,GAAG,MAAM,KAAK,aAAa,CAAC;IAClD;;;;;;;;OAQG;IACH,WAAW,CAAC,EAAE,CAAC,EAAE,EAAE,MAAM,GAAG,MAAM,KAAK,aAAa,CAAC;IACrD,kEAAkE;IAClE,QAAQ,CAAC,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAAC;IAClC;;;;;;;;;;;;;;;OAeG;IACH,aAAa,CAAC,EAAE;QAAE,EAAE,EAAE,MAAM,GAAG,MAAM,CAAC;QAAC,IAAI,EAAE,QAAQ,GAAG,OAAO,CAAA;KAAE,GAAG,IAAI,CAAC;CAC1E;AAID;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,EACpC,KAAK,EACL,QAAQ,GACT,EAAE;IACD,KAAK,EAAE,kBAAkB,CAAC;IAC1B,QAAQ,EAAE,SAAS,CAAC;CACrB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAEpB;AAED;;;;;;GAMG;AACH,wBAAgB,WAAW,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,GAAG;IAChE,SAAS,EAAE,OAAO,CAAC;IACnB,SAAS,EAAE,aAAa,CAAC;IACzB,WAAW,EAAE,aAAa,GAAG,SAAS,CAAC;IACvC,QAAQ,EAAE,OAAO,CAAC;IAClB,0EAA0E;IAC1E,QAAQ,EAAE,QAAQ,GAAG,OAAO,GAAG,IAAI,CAAC;CACrC,CAaA;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,aAAa,CAAC,EAAE,IAAI,EAAE,EAAE;IAAE,IAAI,EAAE,QAAQ,GAAG,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAsBvF;AAED;;;;;;;GAOG;AACH,wBAAgB,UAAU,CAAC,EACzB,WAAW,EACX,KAAK,EACL,MAAM,GACP,EAAE;IACD,WAAW,EAAE,aAAa,GAAG,SAAS,CAAC;IACvC,KAAK,EAAE,OAAO,CAAC;IACf,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA8BpB"}

package/dist/types/components/data-display/DataViews/data-views-empty.d.ts

@@ -0,0 +1,23 @@
+/**
+ * TWO EMPTY STATES, NOT ONE.
+ *
+ * "Nenhum pagamento registrado" under an active filter is a lie, and it is the
+ * expensive kind: the operator reads it as "this store has no payments" and
+ * goes looking for the bug somewhere else. The page's own empty copy answers
+ * "there is nothing here yet"; it cannot answer "nothing matches what you
+ * typed", because it does not know what was typed.
+ *
+ * So the grid renders the FILTERED variant itself — it is the only party that
+ * knows a filter is applied — and defers to the host's `emptyState` only when
+ * the list is genuinely empty. The filtered one carries the way out, which is
+ * the whole point: the fix is one click, and it is right there.
+ */
+export declare function DataViewsEmpty({ filtered, onClearFilters, emptyState, testIdPrefix, }: {
+    /** Is anything narrowing the list right now (search, pills or ranges)? */
+    filtered: boolean;
+    onClearFilters: () => void;
+    /** The page's own copy for a genuinely empty list. */
+    emptyState?: React.ReactNode;
+    testIdPrefix: string;
+}): React.JSX.Element;
+//# sourceMappingURL=data-views-empty.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-empty.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-empty.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-empty.tsx"],"names":[],"mappings":"AASA;;;;;;;;;;;;;GAaG;AACH,wBAAgB,cAAc,CAAC,EAC7B,QAAQ,EACR,cAAc,EACd,UAAU,EACV,YAAY,GACb,EAAE;IACD,0EAA0E;IAC1E,QAAQ,EAAE,OAAO,CAAC;IAClB,cAAc,EAAE,MAAM,IAAI,CAAC;IAC3B,sDAAsD;IACtD,UAAU,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC7B,YAAY,EAAE,MAAM,CAAC;CACtB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAuDpB"}

package/dist/types/components/data-display/DataViews/data-views-export.d.ts

@@ -0,0 +1,62 @@
+import type { DataViewQuery } from "./data-views-types";
+/**
+ * EXPORT — the current QUERY, never the rendered page.
+ *
+ * Exporting what happens to be on screen is the single most common bug in an
+ * admin table: the operator filtered 214 records, sees 25, exports, and gets
+ * 25 — with nothing anywhere saying so. So this control does not touch the
+ * loaded rows at all. It hands the host the same `DataViewQuery` the grid is
+ * showing, unpaginated, and the HOST re-queries the backend — the same
+ * division as everywhere else here: the component emits, the host fetches.
+ *
+ * The menu states the number it is about to export before the click, so the
+ * two possible answers (the selection, or the whole filtered set) are never a
+ * guess.
+ */
+/** What a host can be asked to produce. */
+export type DataViewExportFormat = "xlsx" | "csv" | "json";
+/** The request handed to the host when the operator picks a format. */
+export interface DataViewExportRequest {
+    format: DataViewExportFormat;
+    /**
+     * The live query with `page: 1` and `pageSize` set to the whole matched
+     * total — i.e. "everything this filter selects", not this page.
+     */
+    query: DataViewQuery;
+    /**
+     * The selected row ids, when the operator has a selection. The host filters
+     * the re-queried rows to these; absent means the whole filtered set.
+     */
+    selectedIds?: Array<string | number>;
+    /** The visible columns, in the operator's current order. */
+    columns: {
+        id: string;
+        label: string;
+    }[];
+}
+/** Injected export. Absent ⇒ no Exportar control, exactly like `renderCard`. */
+export interface DataViewExport {
+    /** Runs the export. Awaited, so the trigger can show it is working. */
+    onExport: (request: DataViewExportRequest) => Promise<void> | void;
+    /** Formats to offer, in menu order. Defaults to all three. */
+    formats?: DataViewExportFormat[];
+}
+interface ExportMenuProps {
+    config: DataViewExport;
+    /** The live query — copied and unpaginated before it reaches the host. */
+    query: DataViewQuery;
+    /** The unpaginated total, so the label can state what "tudo" means. */
+    totalCount: number;
+    selectedIds: Array<string | number>;
+    columns: {
+        id: string;
+        label: string;
+    }[];
+    testIdPrefix: string;
+    /** Render icon-only (measured upstream). */
+    compact?: boolean;
+}
+/** The toolbar's Exportar control. Renders nothing when no host wired it. */
+export declare function DataViewsExportMenu({ config, query, totalCount, selectedIds, columns, testIdPrefix, compact, }: ExportMenuProps): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-export.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-export.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-export.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-export.tsx"],"names":[],"mappings":"AAWA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,oBAAoB,CAAC;AAExD;;;;;;;;;;;;;GAaG;AAEH,2CAA2C;AAC3C,MAAM,MAAM,oBAAoB,GAAG,MAAM,GAAG,KAAK,GAAG,MAAM,CAAC;AAE3D,uEAAuE;AACvE,MAAM,WAAW,qBAAqB;IACpC,MAAM,EAAE,oBAAoB,CAAC;IAC7B;;;OAGG;IACH,KAAK,EAAE,aAAa,CAAC;IACrB;;;OAGG;IACH,WAAW,CAAC,EAAE,KAAK,CAAC,MAAM,GAAG,MAAM,CAAC,CAAC;IACrC,4DAA4D;IAC5D,OAAO,EAAE;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,EAAE,CAAC;CAC1C;AAED,gFAAgF;AAChF,MAAM,WAAW,cAAc;IAC7B,uEAAuE;IACvE,QAAQ,EAAE,CAAC,OAAO,EAAE,qBAAqB,KAAK,OAAO,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC;IACnE,8DAA8D;IAC9D,OAAO,CAAC,EAAE,oBAAoB,EAAE,CAAC;CAClC;AAWD,UAAU,eAAe;IACvB,MAAM,EAAE,cAAc,CAAC;IACvB,0EAA0E;IAC1E,KAAK,EAAE,aAAa,CAAC;IACrB,uEAAuE;IACvE,UAAU,EAAE,MAAM,CAAC;IACnB,WAAW,EAAE,KAAK,CAAC,MAAM,GAAG,MAAM,CAAC,CAAC;IACpC,OAAO,EAAE;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,EAAE,CAAC;IACzC,YAAY,EAAE,MAAM,CAAC;IACrB,4CAA4C;IAC5C,OAAO,CAAC,EAAE,OAAO,CAAC;CACnB;AAoID,6EAA6E;AAC7E,wBAAgB,mBAAmB,CAAC,EAClC,MAAM,EACN,KAAK,EACL,UAAU,EACV,WAAW,EACX,OAAO,EACP,YAAY,EACZ,OAAO,GACR,EAAE,eAAe,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA2CrC"}

package/dist/types/components/data-display/DataViews/data-views-filter-panel.d.ts

@@ -0,0 +1,28 @@
+import type { FilterFieldConfig, RangeFieldConfig, RangeValue } from "./data-views-types";
+export interface GridFilterPanelProps<T extends Record<string, unknown>> {
+    testIdPrefix: string;
+    search: string;
+    fields: FilterFieldConfig<T>[];
+    rangeFields: RangeFieldConfig<T>[];
+    pills: Record<string, string[]>;
+    ranges: Record<string, RangeValue>;
+    onSearchChange: (value: string) => void;
+    onTogglePill: (fieldId: string, value: string, checked: boolean) => void;
+    onChangeRange: (fieldId: string, range: RangeValue) => void;
+    onClearField: (fieldId: string) => void;
+    onClearAll: () => void;
+}
+/** The slide-in filter panel: keyword + checkbox facets + numeric ranges. */
+export declare function GridFilterPanel<T extends Record<string, unknown>>(props: GridFilterPanelProps<T>): React.JSX.Element;
+/** Props for the modal filter surface used below the inline breakpoint. */
+interface FilterDialogProps<T extends Record<string, unknown>> extends GridFilterPanelProps<T> {
+    open: boolean;
+    onClose: () => void;
+}
+/**
+ * The same filter controls in a centered modal — used on smaller screens where the
+ * slide-in panel would overlap the table. The "Filtros" toolbar button opens it.
+ */
+export declare function FilterDialog<T extends Record<string, unknown>>({ open, onClose, ...props }: FilterDialogProps<T>): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-filter-panel.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-filter-panel.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-filter-panel.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-filter-panel.tsx"],"names":[],"mappings":"AASA,OAAO,KAAK,EACV,iBAAiB,EACjB,gBAAgB,EAChB,UAAU,EACX,MAAM,oBAAoB,CAAC;AAI5B,MAAM,WAAW,oBAAoB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACrE,YAAY,EAAE,MAAM,CAAC;IACrB,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,iBAAiB,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/B,WAAW,EAAE,gBAAgB,CAAC,CAAC,CAAC,EAAE,CAAC;IACnC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IAChC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,CAAC,CAAC;IACnC,cAAc,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC,YAAY,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,KAAK,IAAI,CAAC;IACzE,aAAa,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,KAAK,IAAI,CAAC;IAC5D,YAAY,EAAE,CAAC,OAAO,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC,UAAU,EAAE,MAAM,IAAI,CAAC;CACxB;AA6FD,6EAA6E;AAC7E,wBAAgB,eAAe,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC/D,KAAK,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAC7B,KAAK,CAAC,GAAG,CAAC,OAAO,CAUnB;AAED,2EAA2E;AAC3E,UAAU,iBAAiB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAE,SAAQ,oBAAoB,CAAC,CAAC,CAAC;IAC5F,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,MAAM,IAAI,CAAC;CACrB;AAED;;;GAGG;AACH,wBAAgB,YAAY,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,EAC9D,IAAI,EACJ,OAAO,EACP,GAAG,KAAK,EACT,EAAE,iBAAiB,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA6B1C"}

package/dist/types/components/data-display/DataViews/data-views-filter.d.ts

@@ -0,0 +1,12 @@
+import type { DataViewColumn, FilterFieldConfig, RangeFieldConfig, RangeValue } from "./data-views-types";
+/**
+ * The rows matching the current search + pill selections + numeric ranges
+ * (order unchanged). `rangeFields` is optional so existing multi-select-only
+ * tables call this unchanged.
+ */
+export declare function filterRows<T extends Record<string, unknown>>(rows: T[], columns: DataViewColumn<T>[], fields: FilterFieldConfig<T>[], criteria: {
+    search: string;
+    pills: Record<string, string[]>;
+    ranges?: Record<string, RangeValue>;
+}, rangeFields?: RangeFieldConfig<T>[]): T[];
+//# sourceMappingURL=data-views-filter.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-filter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-filter.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-filter.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EACV,cAAc,EACd,iBAAiB,EACjB,gBAAgB,EAChB,UAAU,EACX,MAAM,oBAAoB,CAAC;AA8G5B;;;;GAIG;AACH,wBAAgB,UAAU,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC1D,IAAI,EAAE,CAAC,EAAE,EACT,OAAO,EAAE,cAAc,CAAC,CAAC,CAAC,EAAE,EAC5B,MAAM,EAAE,iBAAiB,CAAC,CAAC,CAAC,EAAE,EAC9B,QAAQ,EAAE;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IAAC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,UAAU,CAAC,CAAA;CAAE,EAClG,WAAW,GAAE,gBAAgB,CAAC,CAAC,CAAC,EAAO,GACtC,CAAC,EAAE,CASL"}

package/dist/types/components/data-display/DataViews/data-views-glyphs.d.ts

@@ -0,0 +1,37 @@
+/** Three rows at a given gap — the density preview for the table and list. */
+export declare function RowsGlyph({ gap, active }: {
+    gap: number;
+    active: boolean;
+}): React.JSX.Element;
+/** A dense block grid — the table layout. */
+export declare function TableGlyph({ active }: {
+    active: boolean;
+}): React.JSX.Element;
+/** Full-width rows each carrying a leading mark — the list layout. */
+export declare function ListGlyph({ active }: {
+    active: boolean;
+}): React.JSX.Element;
+/**
+ * A grid of blocks — the cards layout, and ALSO the cards density preview: `n`
+ * is how many fit per row, so "Muitos / Médio / Poucos" is shown rather than
+ * described.
+ */
+export declare function GridGlyph({ n, active }: {
+    n?: number;
+    active: boolean;
+}): React.JSX.Element;
+/**
+ * Full-height columns, `n` of them — the board's DENSITY, where fewer, wider
+ * columns is the comfortable end. Distinct from {@link BoardGlyph}, which
+ * stands for the board format itself and shows cards stacked at differing
+ * depths; this one is about the columns' width, so the bars are solid.
+ */
+export declare function ColumnsGlyph({ n, active }: {
+    n: number;
+    active: boolean;
+}): React.JSX.Element;
+/** Three columns of decreasing height — the board. */
+export declare function BoardGlyph({ active }: {
+    active: boolean;
+}): React.JSX.Element;
+//# sourceMappingURL=data-views-glyphs.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-glyphs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-glyphs.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-glyphs.tsx"],"names":[],"mappings":"AAyBA,8EAA8E;AAC9E,wBAAgB,SAAS,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,EAAE;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAQ9F;AAED,6CAA6C;AAC7C,wBAAgB,UAAU,CAAC,EAAE,MAAM,EAAE,EAAE;IAAE,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAW7E;AAED,sEAAsE;AACtE,wBAAgB,SAAS,CAAC,EAAE,MAAM,EAAE,EAAE;IAAE,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAqB5E;AAED;;;;GAIG;AACH,wBAAgB,SAAS,CAAC,EAAE,CAAK,EAAE,MAAM,EAAE,EAAE;IAAE,CAAC,CAAC,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAQ/F;AAED;;;;;GAKG;AACH,wBAAgB,YAAY,CAAC,EAAE,CAAC,EAAE,MAAM,EAAE,EAAE;IAAE,CAAC,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAQ7F;AAED,sDAAsD;AACtD,wBAAgB,UAAU,CAAC,EAAE,MAAM,EAAE,EAAE;IAAE,MAAM,EAAE,OAAO,CAAA;CAAE,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAY7E"}

package/dist/types/components/data-display/DataViews/data-views-grid-bodies.d.ts

@@ -0,0 +1,23 @@
+import React from "react";
+import { type BoardConfig } from "./DataViewsBoard";
+import { type ListGroupConfig } from "./list-card-rails";
+import type { DataViewCardSelection } from "./data-views-types";
+import type { DataViewsController } from "./use-data-views-state";
+interface GridMainProps<T extends Record<string, unknown>> {
+    c: DataViewsController<T>;
+    getRowId: (row: T) => string | number;
+    renderCard?: (row: T, selection: DataViewCardSelection) => React.ReactNode;
+    /** Opt-in "Lista" layout — one full-width row per record. */
+    renderListRow?: (row: T, selection: DataViewCardSelection) => React.ReactNode;
+    /** The Lista's shared columns. Omitted, each row resolves its own tracks. */
+    listGroup?: ListGroupConfig<T>;
+    /** Opt-in "Quadro" (board) layout — needs `renderCard`, since it reuses the card. */
+    board?: BoardConfig<T>;
+    dataTestId?: string;
+    emptyState?: React.ReactNode;
+    testIdPrefix: string;
+}
+/** Picks the body from the layout context: board, list, cards, or the dense grid. */
+export declare function GridMain<T extends Record<string, unknown>>(props: GridMainProps<T>): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-grid-bodies.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-grid-bodies.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-grid-bodies.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-grid-bodies.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,MAAM,OAAO,CAAC;AAc1B,OAAO,EAAkB,KAAK,WAAW,EAAE,MAAM,kBAAkB,CAAC;AAEpE,OAAO,EAAiB,KAAK,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACxE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,oBAAoB,CAAC;AAChE,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAqOlE,UAAU,aAAa,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACvD,CAAC,EAAE,mBAAmB,CAAC,CAAC,CAAC,CAAC;IAC1B,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,MAAM,CAAC;IACtC,UAAU,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,EAAE,SAAS,EAAE,qBAAqB,KAAK,KAAK,CAAC,SAAS,CAAC;IAC3E,6DAA6D;IAC7D,aAAa,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,EAAE,SAAS,EAAE,qBAAqB,KAAK,KAAK,CAAC,SAAS,CAAC;IAC9E,6EAA6E;IAC7E,SAAS,CAAC,EAAE,eAAe,CAAC,CAAC,CAAC,CAAC;IAC/B,qFAAqF;IACrF,KAAK,CAAC,EAAE,WAAW,CAAC,CAAC,CAAC,CAAC;IACvB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,UAAU,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC7B,YAAY,EAAE,MAAM,CAAC;CACtB;AAgGD,qFAAqF;AACrF,wBAAgB,QAAQ,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,aAAa,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA0BtG"}

package/dist/types/components/data-display/DataViews/data-views-grid-helpers.d.ts

@@ -0,0 +1,73 @@
+import { type GridColumn } from "../DataGrid";
+import { type SortFieldDefinition } from "../../layout/ContentToolbar";
+import type { DataViewColumn, DataViewState, FilterFieldConfig, RangeFieldConfig, RowAction } from "./data-views-types";
+/** Is this the non-clickable actions column? */
+export declare function isActionsColumn<T extends Record<string, unknown>>(col: GridColumn<T>): boolean;
+/**
+ * Map the DataView columns to grid columns, applying visibility and — when a row
+ * click handler is present — wrapping each non-actions cell so clicking opens the row.
+ */
+export declare function buildGridColumns<T extends Record<string, unknown>>(columns: DataViewColumn<T>[], visibleColumns: string[], onRowClick: ((row: T) => void) | undefined): GridColumn<T>[];
+interface ActionsColumnConfig<T extends Record<string, unknown>> {
+    /** Actions that build the auto "⋮" kebab. Ignored when `renderRowMenu` is set. */
+    rowActions: RowAction<T>[];
+    /** Optional leading slot (e.g. a favourite star) rendered before the kebab. */
+    leading?: (row: T) => React.ReactNode;
+    testIdPrefix: string;
+    getRowId: (row: T) => string | number;
+    /**
+     * Escape hatch: render a bespoke per-row menu (e.g. an entity's self-contained
+     * 3-dots menu that owns its own popups) INSTEAD of the auto kebab built from
+     * `rowActions`. This is how the table row and the card share ONE menu component.
+     * `rowActions`/`bulkActions` still drive the multi-row bulk menu, which a
+     * single-row menu intentionally does not replace.
+     */
+    renderRowMenu?: (row: T) => React.ReactNode;
+}
+/**
+ * The auto "⋮" kebab actions column built from the reusable `rowActions` — the
+ * SAME definitions that feed the bulk menu, so the two never drift. Each item
+ * acts on just this row; `rowLabel` provides a per-row label when set. An
+ * optional `leading` slot (e.g. a favourite star) renders before the kebab.
+ * When `renderRowMenu` is supplied, the cell renders that bespoke menu instead.
+ */
+export declare function buildRowActionsColumn<T extends Record<string, unknown>>(config: ActionsColumnConfig<T>): DataViewColumn<T>;
+/** Sort options derived from the sortable columns when a page supplies none. */
+export declare function defaultSortFields<T extends Record<string, unknown>>(columns: DataViewColumn<T>[]): SortFieldDefinition[];
+/** Count active filters (search + selected pills + bounded ranges) for the badge. */
+export declare function computeActiveFilterCount<T extends Record<string, unknown>>(state: DataViewState, fields: FilterFieldConfig<T>[], rangeFields: RangeFieldConfig<T>[]): number;
+interface RenderBulkArgs<T extends Record<string, unknown>> {
+    rowActions: RowAction<T>[] | undefined;
+    bulkActions: ((selectedRows: T[], clearSelection: () => void) => React.ReactNode) | undefined;
+    selectedRows: T[];
+    clearSelection: () => void;
+    testIdPrefix: string;
+}
+/**
+ * The selection bulk control shown in the toolbar. Prefers the reusable
+ * `rowActions` (an "Ações" dropdown mirroring the row kebab); falls back to the
+ * low-level `bulkActions` render prop. Renders nothing with no selection.
+ */
+export declare function renderBulkActions<T extends Record<string, unknown>>({ rowActions, bulkActions, selectedRows, clearSelection, testIdPrefix, }: RenderBulkArgs<T>): React.ReactNode;
+/** Toggle a single value in a pill's selected-list (returns the next list). */
+export declare function togglePillValues(current: string[] | undefined, value: string, checked: boolean): string[];
+/**
+ * The card grid's `grid-template-columns`, as an sx fragment.
+ *
+ * One rule at every width: each card asks for `targetWidth` and `auto-fill`
+ * decides how many fit. Density moves the target, so it changes the count at
+ * every size — which the previous column-count cap could not do, because its
+ * track floor bottomed out at a constant shared by all three densities.
+ *
+ * Below `sm` this is a single column, and no target changes that. That is why
+ * the density control hides itself there rather than offering three settings
+ * that all draw the same thing.
+ */
+export declare function cardGridTracks(targetWidth: number): {
+    gridTemplateColumns: {
+        xs: string;
+        sm: string;
+    };
+};
+export {};
+//# sourceMappingURL=data-views-grid-helpers.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-grid-helpers.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-grid-helpers.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-grid-helpers.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAE,KAAK,UAAU,EAAE,MAAM,aAAa,CAAC;AAC9C,OAAO,EAAE,KAAK,mBAAmB,EAAE,MAAM,6BAA6B,CAAC;AAKvE,OAAO,KAAK,EACV,cAAc,EACd,aAAa,EACb,iBAAiB,EACjB,gBAAgB,EAChB,SAAS,EACV,MAAM,oBAAoB,CAAC;AAE5B,gDAAgD;AAChD,wBAAgB,eAAe,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,GAAG,EAAE,UAAU,CAAC,CAAC,CAAC,GAAG,OAAO,CAE9F;AAED;;;GAGG;AACH,wBAAgB,gBAAgB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAChE,OAAO,EAAE,cAAc,CAAC,CAAC,CAAC,EAAE,EAC5B,cAAc,EAAE,MAAM,EAAE,EACxB,UAAU,EAAE,CAAC,CAAC,GAAG,EAAE,CAAC,KAAK,IAAI,CAAC,GAAG,SAAS,GACzC,UAAU,CAAC,CAAC,CAAC,EAAE,CAoBjB;AAED,UAAU,mBAAmB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IAC7D,kFAAkF;IAClF,UAAU,EAAE,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC;IAC3B,+EAA+E;IAC/E,OAAO,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,KAAK,CAAC,SAAS,CAAC;IACtC,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,MAAM,CAAC;IACtC;;;;;;OAMG;IACH,aAAa,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,KAAK,CAAC,SAAS,CAAC;CAC7C;AAED;;;;;;GAMG;AACH,wBAAgB,qBAAqB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EACrE,MAAM,EAAE,mBAAmB,CAAC,CAAC,CAAC,GAC7B,cAAc,CAAC,CAAC,CAAC,CAqBnB;AA+BD,gFAAgF;AAChF,wBAAgB,iBAAiB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EACjE,OAAO,EAAE,cAAc,CAAC,CAAC,CAAC,EAAE,GAC3B,mBAAmB,EAAE,CAkBvB;AAED,qFAAqF;AACrF,wBAAgB,wBAAwB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EACxE,KAAK,EAAE,aAAa,EACpB,MAAM,EAAE,iBAAiB,CAAC,CAAC,CAAC,EAAE,EAC9B,WAAW,EAAE,gBAAgB,CAAC,CAAC,CAAC,EAAE,GACjC,MAAM,CAQR;AAuCD,UAAU,cAAc,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACxD,UAAU,EAAE,SAAS,CAAC,CAAC,CAAC,EAAE,GAAG,SAAS,CAAC;IACvC,WAAW,EAAE,CAAC,CAAC,YAAY,EAAE,CAAC,EAAE,EAAE,cAAc,EAAE,MAAM,IAAI,KAAK,KAAK,CAAC,SAAS,CAAC,GAAG,SAAS,CAAC;IAC9F,YAAY,EAAE,CAAC,EAAE,CAAC;IAClB,cAAc,EAAE,MAAM,IAAI,CAAC;IAC3B,YAAY,EAAE,MAAM,CAAC;CACtB;AAED;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,EACnE,UAAU,EACV,WAAW,EACX,YAAY,EACZ,cAAc,EACd,YAAY,GACb,EAAE,cAAc,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,SAAS,CAkBrC;AAED,+EAA+E;AAC/E,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,SAAS,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,GAAG,MAAM,EAAE,CAGzG;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,cAAc,CAAC,WAAW,EAAE,MAAM;;;;;EAOjD"}

package/dist/types/components/data-display/DataViews/data-views-grid-parts.d.ts

@@ -0,0 +1,72 @@
+import { type DataViewsLayout } from "./data-views-layout-context";
+import type { ListGroupConfig } from "./list-card-rails";
+import type { DisplayPanelView } from "./data-views-display-panel";
+import type { DataViewExport } from "./data-views-export";
+import type { BoardConfig } from "./DataViewsBoard";
+import { type ScopeConfig } from "./data-views-scopes";
+import type { DataViewCardSelection, FilterFieldConfig, RangeFieldConfig, RowAction } from "./data-views-types";
+import type { DataViewsController } from "./use-data-views-state";
+interface GridShellProps<T extends Record<string, unknown>> {
+    c: DataViewsController<T>;
+    rows: T[];
+    fields: FilterFieldConfig<T>[];
+    rangeFields: RangeFieldConfig<T>[];
+    getRowId: (row: T) => string | number;
+    testIdPrefix: string;
+    dataTestId?: string;
+    emptyState?: React.ReactNode;
+    toolbarRightSlot?: React.ReactNode;
+    rowActions?: RowAction<T>[];
+    bulkActions?: (selectedRows: T[], clearSelection: () => void) => React.ReactNode;
+    /** Opt-in "Grade" (cards) layout: renders each row as an entity-supplied card.
+     *  Omit ⇒ table only (no layout toggle). */
+    renderCard?: (row: T, selection: DataViewCardSelection) => React.ReactNode;
+    /**
+     * Opt-in "Quadro" (board) layout. Needs `renderCard` too — the board reuses
+     * the entity's card, so a board config without one simply offers no board
+     * rather than failing: that is a config gap, not a runtime error.
+     */
+    board?: BoardConfig<T>;
+    /** Opt-in "Lista" layout: one full-width, entity-rendered row per record. */
+    renderListRow?: (row: T, selection: DataViewCardSelection) => React.ReactNode;
+    /** The Lista's shared columns, so its rows line up by construction. */
+    listGroup?: ListGroupConfig<T>;
+    /** The page-level partition rendered as tabs under the toolbar. */
+    scopes?: ScopeConfig[];
+    /**
+     * The row field the scopes partition by. Compared against the board's
+     * `groupBy` so the two are not shown as the same partition twice.
+     */
+    scopeFieldId?: string;
+    /** Per-sort-field value kind, so directions read in the column's own terms. */
+    sortKinds?: Record<string, string>;
+    /** The saved-view chrome bracketing the Exibir panel. */
+    displayView?: DisplayPanelView;
+    /** Injected export — the host re-queries; the grid never fetches. */
+    exportConfig?: DataViewExport;
+    /** Page title in the grid's own header row, above the scopes + toolbar. */
+    title?: string;
+    /** Primary page actions rendered at the header row's right. */
+    headerActions?: React.ReactNode;
+    /** Which layout to show first when the user has expressed no preference (default "table"). */
+    defaultLayout?: DataViewsLayout;
+    /** Pin to `defaultLayout`, ignoring the remembered preference (stories/docs). */
+    ignoreStoredLayout?: boolean;
+    /**
+     * Opt into the responsive inline filter UX: a collapsible filter row below the
+     * toolbar on wide screens and a modal on narrow ones. When false (default),
+     * keep the classic slide-in filter panel opened by the "Filtros" button.
+     */
+    inlineFilters?: boolean;
+    /**
+     * Keep the inline search box on screen even with no filter fields and no
+     * active search. Without it a grid whose only filter IS the search (`fields`
+     * empty) can never OFFER one: the row renders only once a search exists, so
+     * the operator would have to hand-edit the URL to start one. Default false —
+     * every grid that ships filter fields already shows the row.
+     */
+    alwaysShowSearch?: boolean;
+}
+export declare function GridShell<T extends Record<string, unknown>>(props: GridShellProps<T>): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-grid-parts.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-grid-parts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-grid-parts.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-grid-parts.tsx"],"names":[],"mappings":"AASA,OAAO,EAGL,KAAK,eAAe,EACrB,MAAM,6BAA6B,CAAC;AAGrC,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAIzD,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,4BAA4B,CAAC;AACnE,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAG1D,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,kBAAkB,CAAC;AACpD,OAAO,EAAE,KAAK,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAGvD,OAAO,KAAK,EACV,qBAAqB,EACrB,iBAAiB,EACjB,gBAAgB,EAEhB,SAAS,EACV,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAuLlE,UAAU,cAAc,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACxD,CAAC,EAAE,mBAAmB,CAAC,CAAC,CAAC,CAAC;IAC1B,IAAI,EAAE,CAAC,EAAE,CAAC;IACV,MAAM,EAAE,iBAAiB,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/B,WAAW,EAAE,gBAAgB,CAAC,CAAC,CAAC,EAAE,CAAC;IACnC,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,MAAM,CAAC;IACtC,YAAY,EAAE,MAAM,CAAC;IACrB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,UAAU,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC7B,gBAAgB,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACnC,UAAU,CAAC,EAAE,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC;IAC5B,WAAW,CAAC,EAAE,CAAC,YAAY,EAAE,CAAC,EAAE,EAAE,cAAc,EAAE,MAAM,IAAI,KAAK,KAAK,CAAC,SAAS,CAAC;IACjF;gDAC4C;IAC5C,UAAU,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,EAAE,SAAS,EAAE,qBAAqB,KAAK,KAAK,CAAC,SAAS,CAAC;IAC3E;;;;OAIG;IACH,KAAK,CAAC,EAAE,WAAW,CAAC,CAAC,CAAC,CAAC;IACvB,6EAA6E;IAC7E,aAAa,CAAC,EAAE,CAAC,GAAG,EAAE,CAAC,EAAE,SAAS,EAAE,qBAAqB,KAAK,KAAK,CAAC,SAAS,CAAC;IAC9E,uEAAuE;IACvE,SAAS,CAAC,EAAE,eAAe,CAAC,CAAC,CAAC,CAAC;IAC/B,mEAAmE;IACnE,MAAM,CAAC,EAAE,WAAW,EAAE,CAAC;IACvB;;;OAGG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,+EAA+E;IAC/E,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACnC,yDAAyD;IACzD,WAAW,CAAC,EAAE,gBAAgB,CAAC;IAC/B,qEAAqE;IACrE,YAAY,CAAC,EAAE,cAAc,CAAC;IAC9B,2EAA2E;IAC3E,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,+DAA+D;IAC/D,aAAa,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAChC,8FAA8F;IAC9F,aAAa,CAAC,EAAE,eAAe,CAAC;IAChC,iFAAiF;IACjF,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B;;;;OAIG;IACH,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB;;;;;;OAMG;IACH,gBAAgB,CAAC,EAAE,OAAO,CAAC;CAC5B;AAmFD,wBAAgB,SAAS,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,cAAc,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAsCxG"}

package/dist/types/components/data-display/DataViews/data-views-inline-bar.d.ts

@@ -0,0 +1,23 @@
+import type { GridFilterPanelProps } from "./data-views-filter-panel";
+import type { OverflowSplit } from "./data-views-overflow";
+/** Props the inline bar needs (the slide-in panel's, minus its own chrome). */
+type InlineFilterBarProps<T extends Record<string, unknown>> = Pick<GridFilterPanelProps<T>, "testIdPrefix" | "search" | "fields" | "rangeFields" | "pills" | "ranges" | "onSearchChange" | "onTogglePill" | "onChangeRange" | "onClearField" | "onClearAll"> & {
+    /** The measured degradation state, computed once in `GridShell`. */
+    split: OverflowSplit<T>;
+};
+/**
+ * The filter CONTROLS alone — search, the fields that fit, and "Mais N" for the
+ * ones that don't — with no row chrome of its own, because it is rendered ON
+ * the toolbar line rather than under it (`ContentToolbar`'s `leadingControls`).
+ *
+ * The measurement driving the collapse lives on the toolbar ROW, not here —
+ * see the note on `split` below.
+ */
+export declare function InlineFilterControls<T extends Record<string, unknown>>({ testIdPrefix, pills, ranges, search, onSearchChange, onTogglePill, onChangeRange, onClearField, split, onClearAll, activeFilterCount, onControlOpenChange, }: Omit<InlineFilterBarProps<T>, "fields" | "rangeFields"> & {
+    /** How many filters are applied — decides whether "Limpar" is on the bar at all. */
+    activeFilterCount: number;
+    /** Reports a control opening/closing so the shell can freeze the measurement. */
+    onControlOpenChange?: (open: boolean) => void;
+}): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-inline-bar.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-inline-bar.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-inline-bar.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-inline-bar.tsx"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AAEtE,OAAO,KAAK,EAAiB,aAAa,EAAE,MAAM,uBAAuB,CAAC;AAgD1E,+EAA+E;AAC/E,KAAK,oBAAoB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,IAAI,IAAI,CACjE,oBAAoB,CAAC,CAAC,CAAC,EACrB,cAAc,GACd,QAAQ,GACR,QAAQ,GACR,aAAa,GACb,OAAO,GACP,QAAQ,GACR,gBAAgB,GAChB,cAAc,GACd,eAAe,GACf,cAAc,GACd,YAAY,CACf,GAAG;IACF,oEAAoE;IACpE,KAAK,EAAE,aAAa,CAAC,CAAC,CAAC,CAAC;CACzB,CAAC;AA8FF;;;;;;;GAOG;AACH,wBAAgB,oBAAoB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,EACtE,YAAY,EACZ,KAAK,EACL,MAAM,EACN,MAAM,EACN,cAAc,EACd,YAAY,EACZ,aAAa,EACb,YAAY,EACZ,KAAK,EACL,UAAU,EACV,iBAAiB,EACjB,mBAAmB,GACpB,EAAE,IAAI,CAAC,oBAAoB,CAAC,CAAC,CAAC,EAAE,QAAQ,GAAG,aAAa,CAAC,GAAG;IAC3D,oFAAoF;IACpF,iBAAiB,EAAE,MAAM,CAAC;IAC1B,iFAAiF;IACjF,mBAAmB,CAAC,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC;CAC/C,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAqDpB"}