@12-apps/ui 4.1.0 → 5.0.1

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

@@ -0,0 +1,32 @@
+import type { RangeFieldConfig, RangePreset, RangeValue } from "./data-views-types";
+/**
+ * The five windows every date filter wants, resolved when CLICKED.
+ *
+ * Each is a whole calendar unit rather than a unit-to-date: "Este mês" is the
+ * whole month, not the 1st through today. It is what the words say, it matches
+ * the label a merchant reads back on the pill, and it changes nothing for a
+ * dataset with no future rows — while a page that does have them (scheduled
+ * orders) would otherwise hide them under a preset that claims to show the
+ * month.
+ *
+ * The week starts on SUNDAY, following the Brazilian calendar these grids are
+ * read against rather than ISO-8601's Monday.
+ */
+export declare const DAY_RANGE_PRESETS: RangePreset[];
+/**
+ * The presets a field offers: its own, or the calendar defaults for a day field
+ * that declared none. An explicit `[]` means none — a host suppressing them is
+ * saying something, and must not be overridden by the fallback.
+ */
+export declare function presetsFor<T extends Record<string, unknown>>(field: RangeFieldConfig<T>): RangePreset[];
+/** A preset's window, evaluating it if it is time-dependent. */
+export declare function resolvePreset(preset: RangePreset): RangeValue;
+/**
+ * Is this preset the window currently applied?
+ *
+ * Bounds compare as STRINGS because a `number` field's stored bound may have
+ * arrived from an input as `100` while the preset declares `100` — same window,
+ * and `undefined` vs a missing key must read as equal too.
+ */
+export declare function isPresetActive(preset: RangePreset, value: RangeValue): boolean;
+//# sourceMappingURL=data-views-range-presets.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-range-presets.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-range-presets.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,WAAW,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAC;AA8BpF;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,iBAAiB,EAAE,WAAW,EA8C1C,CAAC;AAEF;;;;GAIG;AACH,wBAAgB,UAAU,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC1D,KAAK,EAAE,gBAAgB,CAAC,CAAC,CAAC,GACzB,WAAW,EAAE,CAGf;AAED,gEAAgE;AAChE,wBAAgB,aAAa,CAAC,MAAM,EAAE,WAAW,GAAG,UAAU,CAE7D;AAED;;;;;;GAMG;AACH,wBAAgB,cAAc,CAAC,MAAM,EAAE,WAAW,EAAE,KAAK,EAAE,UAAU,GAAG,OAAO,CAK9E"}

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

@@ -0,0 +1,87 @@
+/**
+ * RANGE FILTERS — the value types, apart from the rest of the DataViews model.
+ *
+ * Split out because `data-views-types` had grown past the file-size gate, and
+ * this is the seam that actually exists: a range is a self-contained little
+ * language (a window, its two kinds, its one-click presets) that the pill, the
+ * overflow panel, the slide-in panel and the fake backend all speak.
+ *
+ * Every one of them still imports from `data-views-types`, which re-exports
+ * these — there is one public name for the model, and moving a type between
+ * files is not a reason to touch a dozen import lines.
+ */
+/**
+ * A selected range for a range filter (either bound optional). Numbers for a
+ * `number` field; `AAAA-MM-DD` day strings for a `day` one — which compare
+ * correctly with `<`/`>` precisely because ISO days sort lexicographically.
+ */
+export interface RangeValue {
+    min?: number | string;
+    max?: number | string;
+}
+/** What a range field measures — the input it renders and the bound it stores. */
+export type RangeFieldKind = "number" | "day";
+/**
+ * A one-click window for a range filter: "Hoje", "Acima de R$ 500".
+ *
+ * `range` is a FUNCTION when the answer depends on when it is clicked and a
+ * literal when it does not. "Hoje" must mean today at the moment of the click,
+ * not at the moment the config object was built — a long-lived admin tab
+ * evaluating it once would go on filtering by the day it was opened.
+ *
+ * What lands in `DataViewState.ranges` is always the RESOLVED window, so a
+ * saved view captures the days "Hoje" meant when it was saved. That is the
+ * honest behaviour for a saved view: it is a stored filter, not a stored
+ * intent, and re-running it later must not silently answer a different
+ * question.
+ */
+export interface RangePreset {
+    /** Stable id, used as the React key and in the preset's test id. */
+    id: string;
+    label: string;
+    range: RangeValue | (() => RangeValue);
+}
+interface RangeFieldBase {
+    /** Stable id; the key under `DataViewState.ranges`. */
+    id: string;
+    label: string;
+    /**
+     * One-click windows offered above the `De`/`Até` inputs.
+     *
+     * A `day` field falls back to the calendar defaults (Hoje / Ontem / Esta
+     * semana / Este mês / Este ano) when this is omitted, because those windows
+     * are the same for every date filter that has ever existed. A `number` field
+     * has no such universal set — what counts as a big order is the host's
+     * business — so it shows presets only when given them. Pass `[]` to a day
+     * field to suppress the defaults.
+     */
+    presets?: RangePreset[];
+}
+/** "Filter by amount": price, stock, margin, order total. */
+export interface NumberRangeFieldConfig<T extends Record<string, unknown>> extends RangeFieldBase {
+    kind?: "number";
+    /** Reads the row's numeric value for this range. */
+    accessor: (row: T) => number | null | undefined;
+    /** Optional unit suffix shown next to the inputs (e.g. "R$", "un"). */
+    unit?: string;
+    /** Numeric input step. Defaults to 1. */
+    step?: number;
+}
+/**
+ * "Filter by period": a pair of INCLUSIVE calendar days, rendered as two native
+ * date inputs. Inclusive is the reason a day range is its own kind rather than a
+ * number over timestamps — coercing an `até` of `2026-07-15` to a instant lands
+ * on that day's midnight and drops the whole final day (FUT-668).
+ */
+export interface DayRangeFieldConfig<T extends Record<string, unknown>> extends RangeFieldBase {
+    kind: "day";
+    /** Reads the row's `AAAA-MM-DD` day for this range. */
+    accessor: (row: T) => string | null | undefined;
+}
+/**
+ * A min/max range filter's configuration. Complements the multi-select pills.
+ * A row with a null/undefined value never matches a bounded range.
+ */
+export type RangeFieldConfig<T extends Record<string, unknown>> = NumberRangeFieldConfig<T> | DayRangeFieldConfig<T>;
+export {};
+//# sourceMappingURL=data-views-range-types.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-range-types.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-range-types.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH;;;;GAIG;AACH,MAAM,WAAW,UAAU;IACzB,GAAG,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;IACtB,GAAG,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC;CACvB;AAED,kFAAkF;AAClF,MAAM,MAAM,cAAc,GAAG,QAAQ,GAAG,KAAK,CAAC;AAE9C;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,WAAW;IAC1B,oEAAoE;IACpE,EAAE,EAAE,MAAM,CAAC;IACX,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,UAAU,GAAG,CAAC,MAAM,UAAU,CAAC,CAAC;CACxC;AAED,UAAU,cAAc;IACtB,uDAAuD;IACvD,EAAE,EAAE,MAAM,CAAC;IACX,KAAK,EAAE,MAAM,CAAC;IACd;;;;;;;;;OASG;IACH,OAAO,CAAC,EAAE,WAAW,EAAE,CAAC;CACzB;AAED,6DAA6D;AAC7D,MAAM,WAAW,sBAAsB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAE,SAAQ,cAAc;IAC/F,IAAI,CAAC,EAAE,QAAQ,CAAC;IAChB,oDAAoD;IACpD,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,IAAI,GAAG,SAAS,CAAC;IAChD,uEAAuE;IACvE,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,yCAAyC;IACzC,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAED;;;;;GAKG;AACH,MAAM,WAAW,mBAAmB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAE,SAAQ,cAAc;IAC5F,IAAI,EAAE,KAAK,CAAC;IACZ,uDAAuD;IACvD,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,IAAI,GAAG,SAAS,CAAC;CACjD;AAED;;;GAGG;AACH,MAAM,MAAM,gBAAgB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,IAC1D,sBAAsB,CAAC,CAAC,CAAC,GACzB,mBAAmB,CAAC,CAAC,CAAC,CAAC"}

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

@@ -0,0 +1,45 @@
+import type { RangeFieldConfig, RangeValue } from "./data-views-types";
+/**
+ * What a range VALUE means, separate from the controls that edit one.
+ *
+ * Pure and component-free: whether a window is set, whether it is inverted, how
+ * it reads as a label, and its numeric form. The pill, the overflow panel and
+ * the filter panel all ask these questions, and none of them should have to
+ * import a component to do it.
+ */
+/** Is either bound set? Drives the pill's active styling and the chip. */
+export declare function isRangeSet(range: RangeValue | undefined): boolean;
+/**
+ * A numeric bound as the merchant writes it: decimal COMMA, thousands grouped.
+ *
+ * `String(17.5)` reads `17.5` — a decimal point in a currency that has none —
+ * and padding it to the field's own precision is what makes `R$ 17,50` instead
+ * of `R$ 17,5`. Shared with the input's blur so the chip and the field it was
+ * typed into can never disagree, which matters because the chip is the ONLY
+ * place the applied window is stated once the popover closes.
+ */
+export declare function formatBoundNumber(amount: number, step?: number): string;
+/**
+ * The chip text for an applied range: "Data: 01/07–31/07" when both ends are
+ * set, and a one-sided window as the inequality it actually is ("Valor: ≥ R$ 20")
+ * rather than an en-dash with a blank side.
+ */
+export declare function rangeChipLabel<T extends Record<string, unknown>>(field: RangeFieldConfig<T>, range: RangeValue): string;
+/**
+ * Is the window INVERTED — a `de` after its `até`?
+ *
+ * Not an error the merchant must clear before the list responds: it simply
+ * matches nothing. But an empty grid with no explanation reads as "there is no
+ * data", so the control says which of the two it is.
+ */
+export declare function isRangeInverted(value: RangeValue): boolean;
+/**
+ * A stored range narrowed to NUMBERS, for the slide-in panel's numeric control.
+ * A bound that doesn't parse is dropped rather than passed on as `NaN`, which
+ * the control would render as an empty box that still filtered.
+ */
+export declare function numericRange(range: RangeValue): {
+    min?: number;
+    max?: number;
+};
+//# sourceMappingURL=data-views-range-values.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-range-values.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-range-values.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAC;AAEvE;;;;;;;GAOG;AAEH,0EAA0E;AAC1E,wBAAgB,UAAU,CAAC,KAAK,EAAE,UAAU,GAAG,SAAS,GAAG,OAAO,CAEjE;AAkBD;;;;;;;;GAQG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE,MAAM,GAAG,MAAM,CAMvE;AAYD;;;;GAIG;AACH,wBAAgB,cAAc,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC9D,KAAK,EAAE,gBAAgB,CAAC,CAAC,CAAC,EAC1B,KAAK,EAAE,UAAU,GAChB,MAAM,CAOR;AACD;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,UAAU,GAAG,OAAO,CAE1D;AACD;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,UAAU,GAAG;IAAE,GAAG,CAAC,EAAE,MAAM,CAAC;IAAC,GAAG,CAAC,EAAE,MAAM,CAAA;CAAE,CAS9E"}

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

@@ -0,0 +1,33 @@
+/**
+ * WHERE THE SCOPE TABS GO, AND WHEN THEY DO NOT GO THERE AT ALL.
+ *
+ * Its own module because it is a placement rule rather than a control: the
+ * strip itself is `DataViewsScopeTabs`, and this decides whether the grid shows
+ * one.
+ */
+import { type ScopeConfig } from "./data-views-scopes";
+/**
+ * The scope tabs — BELOW the toolbar, and absent when the board is already
+ * showing the same partition.
+ *
+ * A "Quadro" grouped by `situacao` is a column per situação; a scope strip over
+ * the same field is a tab per situação. Together they are the same partition
+ * offered twice, one of which silently narrows what the other displays —
+ * picking the "Cancelado" tab leaves a board with one populated column and the
+ * rest empty, which reads as data loss rather than as a filter.
+ *
+ * Only when they partition by the SAME field: a board grouped by one field
+ * beside scopes over another are two different cuts, and both belong.
+ */
+export declare function ScopeTabsSlot({ scopes, scopeFieldId, board, value, onChange, counts, testIdPrefix, }: {
+    scopes: ScopeConfig[];
+    scopeFieldId?: string;
+    board?: {
+        groupBy: string;
+    };
+    value?: string;
+    onChange: (id: string) => void;
+    counts?: Record<string, number>;
+    testIdPrefix: string;
+}): React.JSX.Element | null;
+//# sourceMappingURL=data-views-scope-tabs.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-scope-tabs.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-scope-tabs.tsx"],"names":[],"mappings":"AAEA;;;;;;GAMG;AACH,OAAO,EAAsB,KAAK,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAG3E;;;;;;;;;;;;GAYG;AACH,wBAAgB,aAAa,CAAC,EAC5B,MAAM,EACN,YAAY,EACZ,KAAK,EACL,KAAK,EACL,QAAQ,EACR,MAAM,EACN,YAAY,GACb,EAAE;IACD,MAAM,EAAE,WAAW,EAAE,CAAC;IACtB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,KAAK,CAAC,EAAE;QAAE,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC;IAC5B,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,CAAC,EAAE,EAAE,MAAM,KAAK,IAAI,CAAC;IAC/B,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChC,YAAY,EAAE,MAAM,CAAC;CACtB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,GAAG,IAAI,CAe3B"}

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

@@ -0,0 +1,101 @@
+/**
+ * SCOPES — a page-level partition rendered as a strip of tabs under the toolbar.
+ *
+ * A scope is not a filter. Filters NARROW within the current partition and are
+ * multi-select by design; a scope PARTITIONS and is exclusive. The distinction
+ * is load-bearing for three reasons, and each is why `FilterFieldConfig` could
+ * not express these tabs:
+ *
+ *   1. They are mutually exclusive, and a pill is not.
+ *   2. They carry counts of the WHOLE query, which no client can compute under
+ *      pagination — the count has to come off the response
+ *      ({@link DataViewServer.scopeCounts}).
+ *   3. They compose with the filters instead of competing with them: the scope
+ *      picks the bucket, the pills narrow inside it.
+ *
+ * The `predicate` is deliberately opaque to this package. Only the host knows
+ * what "recusados" selects; the component's whole job is to say WHICH scope is
+ * active and let the server answer.
+ */
+export interface ScopeConfig {
+    /** Stable id — travels in `DataViewQuery.scope` and in a saved view's state. */
+    id: string;
+    label: string;
+    /**
+     * Opaque payload the SERVER interprets. Omitted on the "all" scope. Never read
+     * by this package: a scope is applied at the backend, never in the browser.
+     */
+    predicate?: unknown;
+}
+/**
+ * The active scope id, resolved against what the table currently declares.
+ *
+ * Resolution happens at READ time, on purpose. A saved view is written once and
+ * read many times, and the declared scopes change underneath it — a scope
+ * removed after a view was saved must fall back at render rather than break the
+ * view or, worse, emit a scope the backend rejects. Resolving on write would
+ * bake the mistake in.
+ *
+ * Returns `undefined` when the table declares no scopes, which is what keeps
+ * `scope` out of the emitted query entirely for every table that never opted in.
+ */
+export declare function resolveScope(scopes: ScopeConfig[], stored: string | undefined): string | undefined;
+/**
+ * Reject a table that partitions by a field AND declares a filter pill over the
+ * same field. Two controls over one field is how a tab and a pill end up
+ * contradicting each other — the pill says "estado ∈ {pago, recusado}" while the
+ * tab says "estado = recusado", and nothing in either control can show the user
+ * which one the server honoured.
+ *
+ * Throws in DEVELOPMENT ONLY. A thrown config error in production is strictly
+ * worse than a duplicated control: the duplicate is confusing, the throw is a
+ * blank page. Fail where it is seen and fixed.
+ *
+ * `scopeFieldId` is the field the scopes partition by, when the host knows it.
+ * Absent, the scope IDS are checked against the field ids — which catches the
+ * common shape where the scope ids ARE the field's values (`pago`, `recusado`)
+ * declared a second time as a pill.
+ */
+export declare function assertNoScopePillOverlap(scopes: ScopeConfig[], fieldIds: string[], scopeFieldId?: string): void;
+/**
+ * A development-only warning that scopes need server wiring. Scopes are resolved
+ * and emitted, never applied in the browser: filtering locally would make the
+ * counts, the "N de N" counter and the rendered rows disagree the moment a
+ * second page exists.
+ */
+export declare function warnScopesNeedServer(scopes: ScopeConfig[], hasServer: boolean): void;
+/**
+ * The scope configuration's setup-time checks, run once per configuration rather
+ * than per render: reject a field that is both a scope partition and a filter
+ * pill (development only — see `assertNoScopePillOverlap`), and warn about
+ * scopes declared with no server to apply them.
+ *
+ * In a `useMemo` so a mistake surfaces during the FIRST render, where the stack
+ * still points at the table that made it.
+ */
+export declare function useScopeConfigChecks(scopes: ScopeConfig[], fieldIds: string[], scopeFieldId: string | undefined, hasServer: boolean): void;
+/** Everything the tab strip needs; `counts` is absent when the server omits it. */
+interface DataViewsScopeTabsProps {
+    scopes: ScopeConfig[];
+    /** The RESOLVED active scope id (see {@link resolveScope}). */
+    value: string | undefined;
+    onChange: (id: string) => void;
+    /** Server-supplied per-scope totals. Absent ⇒ tabs render WITHOUT numbers. */
+    counts?: Record<string, number>;
+    testIdPrefix: string;
+}
+/**
+ * The scope strip: a horizontally scrolling tab list under the toolbar.
+ *
+ * It SCROLLS rather than collapsing into a select on a narrow screen, which is
+ * the opposite of what the filter pills do — and deliberately. The counts are
+ * the reason the tabs exist at all; burying them behind a menu costs a tap per
+ * glance, exactly on the device where glancing is the point.
+ *
+ * Counts render verbatim from `counts` — never derived from the loaded page, and
+ * never invented when the key is missing. A missing count means "the server did
+ * not say", which reads honestly as no badge at all.
+ */
+export declare function DataViewsScopeTabs({ scopes, value, onChange, counts, testIdPrefix, }: DataViewsScopeTabsProps): React.JSX.Element | null;
+export {};
+//# sourceMappingURL=data-views-scopes.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-scopes.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-scopes.tsx"],"names":[],"mappings":"AAMA;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,WAAW,WAAW;IAC1B,gFAAgF;IAChF,EAAE,EAAE,MAAM,CAAC;IACX,KAAK,EAAE,MAAM,CAAC;IACd;;;OAGG;IACH,SAAS,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,YAAY,CAAC,MAAM,EAAE,WAAW,EAAE,EAAE,MAAM,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,GAAG,SAAS,CAIlG;AAOD;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,wBAAwB,CACtC,MAAM,EAAE,WAAW,EAAE,EACrB,QAAQ,EAAE,MAAM,EAAE,EAClB,YAAY,CAAC,EAAE,MAAM,GACpB,IAAI,CAUN;AAED;;;;;GAKG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,WAAW,EAAE,EAAE,SAAS,EAAE,OAAO,GAAG,IAAI,CAQpF;AAED;;;;;;;;GAQG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,WAAW,EAAE,EACrB,QAAQ,EAAE,MAAM,EAAE,EAClB,YAAY,EAAE,MAAM,GAAG,SAAS,EAChC,SAAS,EAAE,OAAO,GACjB,IAAI,CAON;AAED,mFAAmF;AACnF,UAAU,uBAAuB;IAC/B,MAAM,EAAE,WAAW,EAAE,CAAC;IACtB,+DAA+D;IAC/D,KAAK,EAAE,MAAM,GAAG,SAAS,CAAC;IAC1B,QAAQ,EAAE,CAAC,EAAE,EAAE,MAAM,KAAK,IAAI,CAAC;IAC/B,8EAA8E;IAC9E,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAChC,YAAY,EAAE,MAAM,CAAC;CACtB;AAoKD;;;;;;;;;;;GAWG;AACH,wBAAgB,kBAAkB,CAAC,EACjC,MAAM,EACN,KAAK,EACL,QAAQ,EACR,MAAM,EACN,YAAY,GACb,EAAE,uBAAuB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,GAAG,IAAI,CAkCpD"}

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

@@ -0,0 +1,36 @@
+/**
+ * The bar's keyword box.
+ *
+ * DEBOUNCED rather than committed on Enter/blur. In server mode every commit is
+ * a round trip, and a box that only fires on blur makes the operator press a
+ * key they were not told about to see any result at all — they type, nothing
+ * happens, and the list looks broken. 350ms is long enough that a word costs
+ * one query, short enough to feel like live search.
+ *
+ * `Escape` clears; the X clears without leaving the box. Both exist because
+ * clearing by selecting-and-deleting is three gestures for the most common
+ * thing anyone does to a search box.
+ */
+export declare function InlineKeyword({ value, onChange, testId, autoFocus, onEscape, fill, }: {
+    value: string;
+    onChange: (value: string) => void;
+    testId?: string;
+    autoFocus?: boolean;
+    /** Called on Escape with the box already empty — the collapsed bar closes it. */
+    onEscape?: () => void;
+    /** Take whatever width there is, with no minimum — see {@link boxWidth}. */
+    fill?: boolean;
+}): React.JSX.Element;
+/**
+ * Step 4 of the ladder: the search as a magnifier.
+ *
+ * Carries a dot when a search is APPLIED. Collapsing a control that is
+ * currently filtering the list, with nothing saying so, is how an operator ends
+ * up staring at 3 rows of 214 and reading it as missing data.
+ */
+export declare function CollapsedSearch({ active, onOpen, testId, }: {
+    active: boolean;
+    onOpen: () => void;
+    testId?: string;
+}): React.JSX.Element;
+//# sourceMappingURL=data-views-search.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-search.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-search.tsx"],"names":[],"mappings":"AAgCA;;;;;;;;;;;;GAYG;AACH,wBAAgB,aAAa,CAAC,EAC5B,KAAK,EACL,QAAQ,EACR,MAAM,EACN,SAAS,EACT,QAAQ,EACR,IAAY,GACb,EAAE;IACD,KAAK,EAAE,MAAM,CAAC;IACd,QAAQ,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IAClC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,iFAAiF;IACjF,QAAQ,CAAC,EAAE,MAAM,IAAI,CAAC;IACtB,4EAA4E;IAC5E,IAAI,CAAC,EAAE,OAAO,CAAC;CAChB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA4DpB;AAED;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,EAC9B,MAAM,EACN,MAAM,EACN,MAAM,GACP,EAAE;IACD,MAAM,EAAE,OAAO,CAAC;IAChB,MAAM,EAAE,MAAM,IAAI,CAAC;IACnB,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAkCpB"}

package/dist/types/components/data-display/DataViews/data-views-select-all-strip.d.ts

@@ -0,0 +1,27 @@
+/**
+ * SELECT-ALL FOR THE LAYOUTS THAT HAVE NO HEADER ROW.
+ *
+ * The table gets this for free: its `<thead>` carries a checkbox, so beginning
+ * a selection is one click on a control that sits with the rows it selects.
+ * The cards, the list and the board have no header at all — so without this
+ * there is NO way to start a selection except clicking an item first, and
+ * "select everything on this page" costs one click per row.
+ *
+ * It is deliberately NOT more toolbar chrome. It sits directly above the
+ * content it selects, which is exactly where the table's `<thead>` checkbox
+ * sits; putting it in the toolbar would separate the control from its object
+ * and would also be the third place in this component that renders a
+ * select-all.
+ *
+ * Renders nothing for an empty page: a select-all over zero rows is a control
+ * that cannot do anything, and reserving its band would make the empty state
+ * sit lower in the cards than it does in the table.
+ */
+export declare function SelectAllStrip<T>({ rows, getRowId, selectedIds, onChange, testIdPrefix, }: {
+    rows: T[];
+    getRowId: (row: T) => string | number;
+    selectedIds: Set<string | number>;
+    onChange: (next: Set<string | number>) => void;
+    testIdPrefix: string;
+}): React.JSX.Element | null;
+//# sourceMappingURL=data-views-select-all-strip.d.ts.map

package/dist/types/components/data-display/DataViews/data-views-select-all-strip.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-select-all-strip.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-select-all-strip.tsx"],"names":[],"mappings":"AAQA;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,cAAc,CAAC,CAAC,EAAE,EAChC,IAAI,EACJ,QAAQ,EACR,WAAW,EACX,QAAQ,EACR,YAAY,GACb,EAAE;IACD,IAAI,EAAE,CAAC,EAAE,CAAC;IACV,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,MAAM,CAAC;IACtC,WAAW,EAAE,GAAG,CAAC,MAAM,GAAG,MAAM,CAAC,CAAC;IAClC,QAAQ,EAAE,CAAC,IAAI,EAAE,GAAG,CAAC,MAAM,GAAG,MAAM,CAAC,KAAK,IAAI,CAAC;IAC/C,YAAY,EAAE,MAAM,CAAC;CACtB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,GAAG,IAAI,CAiE3B"}

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

@@ -0,0 +1,24 @@
+/** The multi-select model, identical in every layout (table, cards, board). */
+interface DataViewsSelection<T> {
+    selectedIds: Set<string | number>;
+    setSelectedIds: (ids: Set<string | number>) => void;
+    /** Add/remove ONE id — what a card's or board card's checkbox calls. */
+    toggleId: (id: string | number) => void;
+    /** The selected rows, narrowed to what is currently rendered. */
+    selectedRows: T[];
+    clearSelection: () => void;
+    selectAll: () => void;
+}
+/**
+ * Owns the DataViews selection. ONE set of ids across every layout, so switching
+ * from the board to the table (or to the cards) keeps exactly the same rows
+ * selected and offers exactly the same bulk actions.
+ *
+ * Extracted from {@link useDataViewsState} for that hook's size budget, and
+ * because `toggleId` needs a functional update: two cards toggled in the same
+ * tick would otherwise both read the pre-render set and the second would drop
+ * the first's change.
+ */
+export declare function useSelection<T>(matched: T[], getRowId: (row: T) => string | number): DataViewsSelection<T>;
+export {};
+//# sourceMappingURL=data-views-selection.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-selection.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-selection.ts"],"names":[],"mappings":"AAIA,+EAA+E;AAC/E,UAAU,kBAAkB,CAAC,CAAC;IAC5B,WAAW,EAAE,GAAG,CAAC,MAAM,GAAG,MAAM,CAAC,CAAC;IAClC,cAAc,EAAE,CAAC,GAAG,EAAE,GAAG,CAAC,MAAM,GAAG,MAAM,CAAC,KAAK,IAAI,CAAC;IACpD,wEAAwE;IACxE,QAAQ,EAAE,CAAC,EAAE,EAAE,MAAM,GAAG,MAAM,KAAK,IAAI,CAAC;IACxC,iEAAiE;IACjE,YAAY,EAAE,CAAC,EAAE,CAAC;IAClB,cAAc,EAAE,MAAM,IAAI,CAAC;IAC3B,SAAS,EAAE,MAAM,IAAI,CAAC;CACvB;AAED;;;;;;;;;GASG;AACH,wBAAgB,YAAY,CAAC,CAAC,EAC5B,OAAO,EAAE,CAAC,EAAE,EACZ,QAAQ,EAAE,CAAC,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,MAAM,GACpC,kBAAkB,CAAC,CAAC,CAAC,CAoBvB"}

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

@@ -0,0 +1,19 @@
+import type { DataViewServer, DataViewState } from "./data-views-types";
+/**
+ * Server-mode wiring extracted from {@link useDataViewsState} (keeps it within
+ * the size/complexity budget): re-fetch on every effective-query change (page
+ * resets to 1) and expose `changePage` for the pagination control. Read the
+ * latest `state`/`server` at fire time so an inline `server` object per render
+ * doesn't loop the effect.
+ */
+export declare function useServerQuery(server: DataViewServer | undefined, state: DataViewState, scope: string | undefined): {
+    changePage: (page: number) => void;
+};
+/** The controller's server-mode derived fields (or client-mode defaults). */
+export declare function serverDerived(server: DataViewServer | undefined, fallbackCount: number): {
+    serverMode: boolean;
+    serverPage: number;
+    serverPageCount: number;
+    serverTotalCount: number;
+};
+//# sourceMappingURL=data-views-server-query.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-server-query.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-server-query.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,cAAc,EAAE,aAAa,EAAE,MAAM,oBAAoB,CAAC;AAExE;;;;;;GAMG;AACH,wBAAgB,cAAc,CAC5B,MAAM,EAAE,cAAc,GAAG,SAAS,EAClC,KAAK,EAAE,aAAa,EACpB,KAAK,EAAE,MAAM,GAAG,SAAS,GACxB;IACD,UAAU,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;CACpC,CAsCA;AAED,6EAA6E;AAC7E,wBAAgB,aAAa,CAC3B,MAAM,EAAE,cAAc,GAAG,SAAS,EAClC,aAAa,EAAE,MAAM,GACpB;IAAE,UAAU,EAAE,OAAO,CAAC;IAAC,UAAU,EAAE,MAAM,CAAC;IAAC,eAAe,EAAE,MAAM,CAAC;IAAC,gBAAgB,EAAE,MAAM,CAAA;CAAE,CAUhG"}

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

@@ -0,0 +1,29 @@
+import type { DisplayPanelView } from "./data-views-display-panel";
+import type { DataViewExport } from "./data-views-export";
+import type { RowAction } from "./data-views-types";
+import type { DataViewsController } from "./use-data-views-state";
+/**
+ * The toolbar band, fed from the controller. Split out of `GridShell` for that
+ * function's size budget — it is ~25 props of pure forwarding and nothing else.
+ */
+export declare function ShellToolbar<T extends Record<string, unknown>>({ c, rows, testIdPrefix, rowActions, bulkActions, toolbarRightSlot, showInline, compactControls, counterHidden, sortKinds, displayView, exportConfig, filterControls, barRef, }: {
+    c: DataViewsController<T>;
+    rows: T[];
+    testIdPrefix: string;
+    sortKinds?: Record<string, string>;
+    displayView?: DisplayPanelView;
+    exportConfig?: DataViewExport;
+    rowActions?: RowAction<T>[];
+    bulkActions?: (selectedRows: T[], clearSelection: () => void) => React.ReactNode;
+    toolbarRightSlot?: React.ReactNode;
+    /** Search + filters, rendered on the toolbar line (see `GridToolbar`). */
+    filterControls?: React.ReactNode;
+    barRef?: React.Ref<HTMLDivElement>;
+    showInline: boolean;
+    /** Step 2 of the ladder: Exibir/Exportar as icons only. */
+    compactControls?: boolean;
+    /** Step 5, last resort: drop the counter so the row still fits one line. */
+    counterHidden?: boolean;
+}): React.JSX.Element;
+/** Wires the controller into the shared toolbar + filter panel + grid/cards body. */
+//# sourceMappingURL=data-views-shell-toolbar.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-shell-toolbar.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-shell-toolbar.tsx"],"names":[],"mappings":"AAQA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,4BAA4B,CAAC;AACnE,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAE1D,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAElE;;;GAGG;AACH,wBAAgB,YAAY,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,EAC9D,CAAC,EACD,IAAI,EACJ,YAAY,EACZ,UAAU,EACV,WAAW,EACX,gBAAgB,EAChB,UAAU,EACV,eAAe,EACf,aAAa,EACb,SAAS,EACT,WAAW,EACX,YAAY,EACZ,cAAc,EACd,MAAM,GACP,EAAE;IACD,CAAC,EAAE,mBAAmB,CAAC,CAAC,CAAC,CAAC;IAC1B,IAAI,EAAE,CAAC,EAAE,CAAC;IACV,YAAY,EAAE,MAAM,CAAC;IACrB,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACnC,WAAW,CAAC,EAAE,gBAAgB,CAAC;IAC/B,YAAY,CAAC,EAAE,cAAc,CAAC;IAC9B,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,gBAAgB,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACnC,0EAA0E;IAC1E,cAAc,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACjC,MAAM,CAAC,EAAE,KAAK,CAAC,GAAG,CAAC,cAAc,CAAC,CAAC;IACnC,UAAU,EAAE,OAAO,CAAC;IACpB,2DAA2D;IAC3D,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,4EAA4E;IAC5E,aAAa,CAAC,EAAE,OAAO,CAAC;CACzB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAqCpB;AAED,qFAAqF"}

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

@@ -0,0 +1,50 @@
+import { type DataViewColumn, type DataViewState, type FilterFieldConfig, type SavedViewSummary } from "./data-views-types";
+import { type SaveViewPayload } from "./SaveViewModal";
+/**
+ * A rejected pin/share/default/delete surfaced inline (FUT-100) — the menus
+ * close on click, so this Alert is the only signal that survives the action.
+ */
+export declare function ViewMutationErrorAlert({ error, onClose, testIdPrefix, }: {
+    error: string | null;
+    onClose: () => void;
+    testIdPrefix: string;
+}): React.JSX.Element | null;
+interface ViewsMenuSlotProps {
+    views: SavedViewSummary[];
+    /** Name of the currently-applied view, shown in the trigger instead of "Visões". */
+    activeViewName?: string;
+    applyView: (view: SavedViewSummary) => void;
+    /** Reset to the built-in no-filter "Main vision" default. */
+    selectMain: () => void;
+    openCreate: () => void;
+    openEdit: (view: SavedViewSummary) => void;
+    handleDelete: (view: SavedViewSummary) => void;
+    patchView: (view: SavedViewSummary, changes: Partial<Pick<SavedViewSummary, "isDefault" | "pinned" | "shared">>) => Promise<void>;
+    onManageAll: () => void;
+    testIdPrefix: string;
+}
+/**
+ * The saved-views Connector (FUT-89): binds the backend-backed SavedView state +
+ * mutations to the stateless `@12-apps/ui` SavedViewsMenu. All persistence lives here
+ * (via the passed handlers); the UI component itself stays data-free.
+ */
+export declare function ViewsMenuSlot({ views, activeViewName, applyView, selectMain, openCreate, openEdit, handleDelete, patchView, onManageAll, testIdPrefix, }: ViewsMenuSlotProps): React.JSX.Element;
+interface ViewDialogsProps<T extends Record<string, unknown>> {
+    saveOpen: boolean;
+    onCloseSave: () => void;
+    currentState: DataViewState;
+    fields: FilterFieldConfig<T>[];
+    columns: DataViewColumn<T>[];
+    editing: SavedViewSummary | null;
+    onSave: (payload: SaveViewPayload) => Promise<void>;
+    manageOpen: boolean;
+    onCloseManage: () => void;
+    views: SavedViewSummary[];
+    onEditFromManage: (view: SavedViewSummary) => void;
+    onDelete: (view: SavedViewSummary) => void;
+    testIdPrefix: string;
+}
+/** The save-view modal + the manage-views dialog (FUT-89). */
+export declare function ViewDialogs<T extends Record<string, unknown>>({ saveOpen, onCloseSave, currentState, fields, columns, editing, onSave, manageOpen, onCloseManage, views, onEditFromManage, onDelete, testIdPrefix, }: ViewDialogsProps<T>): React.JSX.Element;
+export {};
+//# sourceMappingURL=data-views-table-parts.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-table-parts.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-table-parts.tsx"],"names":[],"mappings":"AAKA,OAAO,EACL,KAAK,cAAc,EACnB,KAAK,aAAa,EAClB,KAAK,iBAAiB,EACtB,KAAK,gBAAgB,EACtB,MAAM,oBAAoB,CAAC;AAE5B,OAAO,EAAiB,KAAK,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAEtE;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,EACrC,KAAK,EACL,OAAO,EACP,YAAY,GACb,EAAE;IACD,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,OAAO,EAAE,MAAM,IAAI,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;CACtB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,GAAG,IAAI,CAc3B;AAED,UAAU,kBAAkB;IAC1B,KAAK,EAAE,gBAAgB,EAAE,CAAC;IAC1B,oFAAoF;IACpF,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,SAAS,EAAE,CAAC,IAAI,EAAE,gBAAgB,KAAK,IAAI,CAAC;IAC5C,6DAA6D;IAC7D,UAAU,EAAE,MAAM,IAAI,CAAC;IACvB,UAAU,EAAE,MAAM,IAAI,CAAC;IACvB,QAAQ,EAAE,CAAC,IAAI,EAAE,gBAAgB,KAAK,IAAI,CAAC;IAC3C,YAAY,EAAE,CAAC,IAAI,EAAE,gBAAgB,KAAK,IAAI,CAAC;IAC/C,SAAS,EAAE,CACT,IAAI,EAAE,gBAAgB,EACtB,OAAO,EAAE,OAAO,CAAC,IAAI,CAAC,gBAAgB,EAAE,WAAW,GAAG,QAAQ,GAAG,QAAQ,CAAC,CAAC,KACxE,OAAO,CAAC,IAAI,CAAC,CAAC;IACnB,WAAW,EAAE,MAAM,IAAI,CAAC;IACxB,YAAY,EAAE,MAAM,CAAC;CACtB;AAED;;;;GAIG;AACH,wBAAgB,aAAa,CAAC,EAC5B,KAAK,EACL,cAAc,EACd,SAAS,EACT,UAAU,EACV,UAAU,EACV,QAAQ,EACR,YAAY,EACZ,SAAS,EACT,WAAW,EACX,YAAY,GACb,EAAE,kBAAkB,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAiBxC;AAED,UAAU,gBAAgB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IAC1D,QAAQ,EAAE,OAAO,CAAC;IAClB,WAAW,EAAE,MAAM,IAAI,CAAC;IACxB,YAAY,EAAE,aAAa,CAAC;IAC5B,MAAM,EAAE,iBAAiB,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/B,OAAO,EAAE,cAAc,CAAC,CAAC,CAAC,EAAE,CAAC;IAC7B,OAAO,EAAE,gBAAgB,GAAG,IAAI,CAAC;IACjC,MAAM,EAAE,CAAC,OAAO,EAAE,eAAe,KAAK,OAAO,CAAC,IAAI,CAAC,CAAC;IACpD,UAAU,EAAE,OAAO,CAAC;IACpB,aAAa,EAAE,MAAM,IAAI,CAAC;IAC1B,KAAK,EAAE,gBAAgB,EAAE,CAAC;IAC1B,gBAAgB,EAAE,CAAC,IAAI,EAAE,gBAAgB,KAAK,IAAI,CAAC;IACnD,QAAQ,EAAE,CAAC,IAAI,EAAE,gBAAgB,KAAK,IAAI,CAAC;IAC3C,YAAY,EAAE,MAAM,CAAC;CACtB;AAED,8DAA8D;AAC9D,wBAAgB,WAAW,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,EAC7D,QAAQ,EACR,WAAW,EACX,YAAY,EACZ,MAAM,EACN,OAAO,EACP,OAAO,EACP,MAAM,EACN,UAAU,EACV,aAAa,EACb,KAAK,EACL,gBAAgB,EAChB,QAAQ,EACR,YAAY,GACb,EAAE,gBAAgB,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CA4BzC"}

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

@@ -0,0 +1,62 @@
+import { type ColumnVisibilityOption, type SortFieldDefinition } from "../../layout/ContentToolbar";
+import { type DisplayPanelView } from "./data-views-display-panel";
+import { type DataViewExport } from "./data-views-export";
+import type { RowAction } from "./data-views-types";
+import type { DataViewsController } from "./use-data-views-state";
+export interface GridToolbarProps<T extends Record<string, unknown>> {
+    testIdPrefix: string;
+    selectedRows: T[];
+    selectAll: () => void;
+    clearSelection: () => void;
+    rowActions?: RowAction<T>[];
+    bulkActions?: (selectedRows: T[], clearSelection: () => void) => React.ReactNode;
+    sortFields: SortFieldDefinition[];
+    activeSortField: string;
+    activeSortOrder: "asc" | "desc";
+    onChangeSort: (field: string, order: "asc" | "desc") => void;
+    matchedCount: number;
+    totalCount: number;
+    toolbarRightSlot?: React.ReactNode;
+    columnOptions: ColumnVisibilityOption[];
+    onToggleColumn: (id: string, visible: boolean) => void;
+    filterOpen: boolean;
+    setFilterOpen: (open: boolean) => void;
+    activeFilterCount: number;
+    /** Hide the "Filtros" slide-in trigger (compact layout shows filters inline). */
+    showFilterTrigger?: boolean;
+    /**
+     * Search + filter controls, rendered ON the toolbar line rather than on a row
+     * beneath it. Absent ⇒ the toolbar keeps its plain two-cluster shape.
+     */
+    filterControls?: React.ReactNode;
+    /** Measures the toolbar ROW for the filter overflow — see `useFilterOverflow`. */
+    barRef?: React.Ref<HTMLDivElement>;
+    /** The controller, so "Exibir" can drive sort, columns, order and format. */
+    c: DataViewsController<T>;
+    /** 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, when the host has views. */
+    displayView?: DisplayPanelView;
+    /** Injected export. Absent ⇒ no Exportar control. */
+    exportConfig?: DataViewExport;
+    /**
+     * Step 2 of the degradation ladder: Exibir/Exportar as icons only.
+     * MEASURED upstream (see `useFilterOverflow`) rather than switched at a
+     * breakpoint, so a two-filter page keeps its labels where a five-filter one
+     * has already given them up.
+     */
+    compactControls?: boolean;
+    /**
+     * Step 5 of the ladder, and its floor: on a screen too narrow for even the
+     * fully-collapsed row, the counter is dropped so the controls still fit one
+     * line instead of spilling outside the toolbar.
+     */
+    counterHidden?: boolean;
+}
+/**
+ * The bordered toolbar band: selection chrome + Sort By, the result counter, the
+ * saved-views slot, and the filter funnel. The negative margin lets the top/bottom
+ * separators reach the sidebar's vertical line and the window edge.
+ */
+export declare function GridToolbar<T extends Record<string, unknown>>(props: GridToolbarProps<T>): React.JSX.Element;
+//# sourceMappingURL=data-views-toolbar.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"data-views-toolbar.d.ts","sourceRoot":"","sources":["../../../../../src/components/data-display/DataViews/data-views-toolbar.tsx"],"names":[],"mappings":"AAIA,OAAO,EAGL,KAAK,sBAAsB,EAC3B,KAAK,mBAAmB,EACzB,MAAM,6BAA6B,CAAC;AAIrC,OAAO,EAAyB,KAAK,gBAAgB,EAAE,MAAM,4BAA4B,CAAC;AAC1F,OAAO,EAAuB,KAAK,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAE/E,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,wBAAwB,CAAC;AAElE,MAAM,WAAW,gBAAgB,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IACjE,YAAY,EAAE,MAAM,CAAC;IACrB,YAAY,EAAE,CAAC,EAAE,CAAC;IAClB,SAAS,EAAE,MAAM,IAAI,CAAC;IACtB,cAAc,EAAE,MAAM,IAAI,CAAC;IAC3B,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,UAAU,EAAE,mBAAmB,EAAE,CAAC;IAClC,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,KAAK,GAAG,MAAM,CAAC;IAChC,YAAY,EAAE,CAAC,KAAK,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,GAAG,MAAM,KAAK,IAAI,CAAC;IAC7D,YAAY,EAAE,MAAM,CAAC;IACrB,UAAU,EAAE,MAAM,CAAC;IACnB,gBAAgB,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACnC,aAAa,EAAE,sBAAsB,EAAE,CAAC;IACxC,cAAc,EAAE,CAAC,EAAE,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,KAAK,IAAI,CAAC;IACvD,UAAU,EAAE,OAAO,CAAC;IACpB,aAAa,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC;IACvC,iBAAiB,EAAE,MAAM,CAAC;IAC1B,iFAAiF;IACjF,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B;;;OAGG;IACH,cAAc,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACjC,kFAAkF;IAClF,MAAM,CAAC,EAAE,KAAK,CAAC,GAAG,CAAC,cAAc,CAAC,CAAC;IACnC,6EAA6E;IAC7E,CAAC,EAAE,mBAAmB,CAAC,CAAC,CAAC,CAAC;IAC1B,+EAA+E;IAC/E,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACnC,kFAAkF;IAClF,WAAW,CAAC,EAAE,gBAAgB,CAAC;IAC/B,qDAAqD;IACrD,YAAY,CAAC,EAAE,cAAc,CAAC;IAC9B;;;;;OAKG;IACH,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B;;;;OAIG;IACH,aAAa,CAAC,EAAE,OAAO,CAAC;CACzB;AAgED;;;;GAIG;AACH,wBAAgB,WAAW,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,gBAAgB,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,OAAO,CAoC5G"}