@flamingo-stack/openframe-frontend-core 0.0.711 → 0.0.712

package/dist/components/features/devices/device-selector/narrowing.d.ts

@@ -0,0 +1,13 @@
+import type { DeviceFilterInput } from '../types';
+import type { DeviceSelectorNarrowing } from './device-selector.types';
+export declare const EMPTY_NARROWING: DeviceSelectorNarrowing;
+/**
+ * Turns the picker's narrowing vocabulary into the backend's.
+ *
+ * The component speaks in table column filters and `key:value` chips because
+ * that is what its controls produce; the owner's device fields take a
+ * `DeviceFilterInput`. A plain-text chip (no colon) stays on screen but carries
+ * no filter, same as the devices page.
+ */
+export declare function narrowingToFilter(narrowing: DeviceSelectorNarrowing): DeviceFilterInput;
+//# sourceMappingURL=narrowing.d.ts.map

package/dist/components/features/devices/device-selector/narrowing.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"narrowing.d.ts","sourceRoot":"","sources":["../../../../../src/components/features/devices/device-selector/narrowing.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,UAAU,CAAC;AAClD,OAAO,KAAK,EAAE,uBAAuB,EAAE,MAAM,yBAAyB,CAAC;AAEvE,eAAO,MAAM,eAAe,EAAE,uBAAyD,CAAC;AAExF;;;;;;;GAOG;AACH,wBAAgB,iBAAiB,CAAC,SAAS,EAAE,uBAAuB,GAAG,iBAAiB,CAmBvF"}

package/dist/components/features/devices/device-selector/use-device-selector.d.ts

@@ -0,0 +1,17 @@
+import type { DeviceRow } from '../types';
+import type { SubTab } from './device-selector.types';
+interface UseDeviceSelectorParams<T extends DeviceRow> {
+    devices: T[];
+    selectedIds: Set<string>;
+    getDeviceKey: (device: T) => string | undefined;
+}
+export declare function useDeviceSelector<T extends DeviceRow>({ devices, selectedIds, getDeviceKey, }: UseDeviceSelectorParams<T>): {
+    searchTerm: string;
+    setSearchTerm: import("react").Dispatch<import("react").SetStateAction<string>>;
+    activeSubTab: SubTab;
+    handleTabChange: (tabId: string) => void;
+    filteredDevices: T[];
+    displayDevices: T[];
+};
+export {};
+//# sourceMappingURL=use-device-selector.d.ts.map

package/dist/components/features/devices/device-selector/use-device-selector.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"use-device-selector.d.ts","sourceRoot":"","sources":["../../../../../src/components/features/devices/device-selector/use-device-selector.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,UAAU,CAAC;AAC1C,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AAEtD,UAAU,uBAAuB,CAAC,CAAC,SAAS,SAAS;IACnD,OAAO,EAAE,CAAC,EAAE,CAAC;IACb,WAAW,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACzB,YAAY,EAAE,CAAC,MAAM,EAAE,CAAC,KAAK,MAAM,GAAG,SAAS,CAAC;CACjD;AAED,wBAAgB,iBAAiB,CAAC,CAAC,SAAS,SAAS,EAAE,EACrD,OAAO,EACP,WAAW,EACX,YAAY,GACb,EAAE,uBAAuB,CAAC,CAAC,CAAC;;;;6BAsBiB,MAAM;;;EAanD"}

package/dist/components/features/devices/device-status.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Device status configuration utilities
+ * Provides consistent status mapping across the application
+ */
+import type { OSPlatformId } from '../../../utils/os-platforms';
+export type DeviceStatusVariant = 'success' | 'error' | 'warning' | 'grey' | 'critical';
+export type DeviceCardStatus = 'active' | 'inactive' | 'offline' | 'warning' | 'error';
+export interface DeviceStatusConfig {
+    label: string;
+    variant: DeviceStatusVariant;
+    cardStatus: DeviceCardStatus;
+}
+/**
+ * Get status configuration for display
+ * Used by both table and grid views for consistent status representation
+ */
+export declare function getDeviceStatusConfig(status: string | null | undefined): DeviceStatusConfig;
+/**
+ * Get operating system type for DeviceCard component
+ * Uses centralized OS type system from ui-kit
+ */
+export declare function getDeviceOperatingSystem(osType?: string): OSPlatformId | undefined;
+//# sourceMappingURL=device-status.d.ts.map

package/dist/components/features/devices/device-status.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"device-status.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/device-status.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAGhE,MAAM,MAAM,mBAAmB,GAAG,SAAS,GAAG,OAAO,GAAG,SAAS,GAAG,MAAM,GAAG,UAAU,CAAC;AACxF,MAAM,MAAM,gBAAgB,GAAG,QAAQ,GAAG,UAAU,GAAG,SAAS,GAAG,SAAS,GAAG,OAAO,CAAC;AAEvF,MAAM,WAAW,kBAAkB;IACjC,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,mBAAmB,CAAC;IAC7B,UAAU,EAAE,gBAAgB,CAAC;CAC9B;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,kBAAkB,CAsE3F;AAED;;;GAGG;AACH,wBAAgB,wBAAwB,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,YAAY,GAAG,SAAS,CAIlF"}

package/dist/components/features/devices/device-statuses.d.ts

@@ -0,0 +1,40 @@
+import type { DeviceFilterInput } from './types';
+/**
+ * Default visible device statuses (excludes ARCHIVED and DELETED).
+ * Deleted devices live on the dedicated /devices/archive page as read-only
+ * records. Use this constant for all device queries that should show "active"
+ * devices only.
+ *
+ * NOTE: If new statuses are added to the backend, they must be added here
+ * to appear in default views.
+ */
+export declare const DEVICE_STATUS: {
+    readonly ONLINE: "ONLINE";
+    readonly OFFLINE: "OFFLINE";
+    readonly ACTIVE: "ACTIVE";
+    readonly INACTIVE: "INACTIVE";
+    readonly MAINTENANCE: "MAINTENANCE";
+    readonly DECOMMISSIONED: "DECOMMISSIONED";
+    readonly PENDING: "PENDING";
+    readonly PENDING_DELETION: "PENDING_DELETION";
+    readonly ARCHIVED: "ARCHIVED";
+    readonly DELETED: "DELETED";
+};
+export type DeviceStatus = (typeof DEVICE_STATUS)[keyof typeof DEVICE_STATUS];
+export declare const DEFAULT_VISIBLE_STATUSES: ["ONLINE", "OFFLINE", "PENDING", "PENDING_DELETION"];
+export declare const DEFAULT_DASHBOARD_STATUSES: ["ONLINE", "OFFLINE", "PENDING", "PENDING_DELETION", "ARCHIVED", "DELETED"];
+export declare const DEFAULT_DEVICES_LIST_STATUSES: ["ONLINE", "OFFLINE", "PENDING_DELETION"];
+export declare const DEVICE_ENRICHMENT_STATUSES: ["ONLINE", "OFFLINE", "ARCHIVED", "DELETED"];
+/**
+ * The device-registry filter the monitoring tables read: the enrichment statuses
+ * as a ready `DeviceFilterInput`. Shared so the policy and query tables ask for
+ * the same fleet and therefore share one cached fetch.
+ */
+export declare const DEVICE_ENRICHMENT_FILTER: DeviceFilterInput;
+export type DefaultVisibleStatus = (typeof DEFAULT_VISIBLE_STATUSES)[number];
+/**
+ * Statuses that are hidden by default (for documentation/reference)
+ */
+export declare const HIDDEN_DEVICE_STATUSES: readonly ["ARCHIVED", "DELETED"];
+export type HiddenDeviceStatus = (typeof HIDDEN_DEVICE_STATUSES)[number];
+//# sourceMappingURL=device-statuses.d.ts.map

package/dist/components/features/devices/device-statuses.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"device-statuses.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/device-statuses.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,SAAS,CAAC;AAEjD;;;;;;;;GAQG;AAEH,eAAO,MAAM,aAAa;;;;;;;;;;;CAiBhB,CAAC;AAEX,MAAM,MAAM,YAAY,GAAG,CAAC,OAAO,aAAa,CAAC,CAAC,MAAM,OAAO,aAAa,CAAC,CAAC;AAE9E,eAAO,MAAM,wBAAwB,sDAKR,CAAC;AAI9B,eAAO,MAAM,0BAA0B,6EAOV,CAAC;AAO9B,eAAO,MAAM,6BAA6B,2CAIb,CAAC;AAM9B,eAAO,MAAM,0BAA0B,8CAKV,CAAC;AAE9B;;;;GAIG;AACH,eAAO,MAAM,wBAAwB,EAAE,iBAAiE,CAAC;AAEzG,MAAM,MAAM,oBAAoB,GAAG,CAAC,OAAO,wBAAwB,CAAC,CAAC,MAAM,CAAC,CAAC;AAE7E;;GAEG;AACH,eAAO,MAAM,sBAAsB,kCAA2D,CAAC;AAE/F,MAAM,MAAM,kBAAkB,GAAG,CAAC,OAAO,sBAAsB,CAAC,CAAC,MAAM,CAAC,CAAC"}

package/dist/components/features/devices/device-tags-filter-button.d.ts

@@ -0,0 +1,22 @@
+/**
+ * The "Device Tags" filter trigger: labelled from md, icon-only below it.
+ *
+ * Breakpoint decided in CSS, and that is the point. Both call sites used to branch
+ * on a `useMdUp()` value threaded down as a prop, and that hook answers `undefined`
+ * until an effect has run, so `isMdUp ? labelled : iconOnly` took the icon-only
+ * arm on the FIRST render at every width, server included. On desktop the button
+ * appeared as a bare square and grew its label a frame later, which also nudged the
+ * search input beside it.
+ *
+ * Two buttons rather than one with a hidden label: `size="icon"` is not just "no
+ * text", it is a square box (`w-11 content-md:w-12`), uniform padding and a smaller glyph
+ * below md. Reproducing that on a `size="default"` button would mean four
+ * `max-md:` overrides fighting the lib's cva variants; letting each variant render
+ * itself and hiding one in CSS keeps both exactly as the design system defines them.
+ * Only one is ever visible, and neither is interactive while hidden (`display: none`
+ * removes it from the tab order).
+ */
+export declare function DeviceTagsFilterButton({ onClick }: {
+    onClick: () => void;
+}): import("react").JSX.Element;
+//# sourceMappingURL=device-tags-filter-button.d.ts.map

package/dist/components/features/devices/device-tags-filter-button.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"device-tags-filter-button.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/device-tags-filter-button.tsx"],"names":[],"mappings":"AAKA;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,sBAAsB,CAAC,EAAE,OAAO,EAAE,EAAE;IAAE,OAAO,EAAE,MAAM,IAAI,CAAA;CAAE,+BAyB1E"}

package/dist/components/features/devices/device-type-icon.d.ts

@@ -0,0 +1,11 @@
+import type React from 'react';
+/**
+ * Returns the icon for a device type (desktop / laptop / server / mobile / tablet),
+ * using the current icons-v2 set. Replaces the deprecated `getDeviceTypeIcon` from
+ * the core library.
+ *
+ * Returns `undefined` for unknown / missing types so the caller can skip rendering.
+ * A row that names a device draws it through `DeviceTypeTile`.
+ */
+export declare function renderDeviceTypeIcon(type?: string, className?: string): React.ReactNode;
+//# sourceMappingURL=device-type-icon.d.ts.map

package/dist/components/features/devices/device-type-icon.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"device-type-icon.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/device-type-icon.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAK/B;;;;;;;GAOG;AACH,wBAAgB,oBAAoB,CAAC,IAAI,CAAC,EAAE,MAAM,EAAE,SAAS,GAAE,MAA2B,GAAG,KAAK,CAAC,SAAS,CAe3G"}

package/dist/components/features/devices/device-type-tile.d.ts

@@ -0,0 +1,9 @@
+/**
+ * A device's type icon in its 32px tile, the leading mark of every row that
+ * names a device. Card-filled, so it keeps its edge on any row ground; an
+ * unknown type draws the monitor rather than an empty tile.
+ */
+export declare function DeviceTypeTile({ type }: {
+    type: string | null | undefined;
+}): import("react").JSX.Element;
+//# sourceMappingURL=device-type-tile.d.ts.map

package/dist/components/features/devices/device-type-tile.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"device-type-tile.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/device-type-tile.tsx"],"names":[],"mappings":"AAKA;;;;GAIG;AACH,wBAAgB,cAAc,CAAC,EAAE,IAAI,EAAE,EAAE;IAAE,IAAI,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,CAAA;CAAE,+BAM3E"}

package/dist/components/features/devices/devices-filter-toolbar.d.ts

@@ -0,0 +1,46 @@
+import type { ComponentProps, Ref } from 'react';
+import { FilterModal, type TagSearchOption } from '../../ui';
+type FilterModalProps = ComponentProps<typeof FilterModal>;
+export interface DevicesFilterToolbarProps {
+    /** Search input, current value (debounce/URL sync owned by the parent). */
+    searchValue: string;
+    onSearchChange: (value: string) => void;
+    /** Already-selected tag chips rendered inside the search input. */
+    tags: TagSearchOption<string>[];
+    onTagRemove: (value: string) => void;
+    onClearAll: () => void;
+    onSubmit: (value: string) => void;
+    /** Open the Device Tags modal. */
+    onOpenFilterModal: () => void;
+    /** FilterModal state, proxied straight through. */
+    isFilterModalOpen: boolean;
+    onCloseFilterModal: () => void;
+    filterGroups: FilterModalProps['filterGroups'];
+    onFilterChange: FilterModalProps['onFilterChange'];
+    currentFilters?: FilterModalProps['currentFilters'];
+    tagFilterKeys: FilterModalProps['tagFilterKeys'];
+    selectedTags: FilterModalProps['selectedTags'];
+    onTagsChange: FilterModalProps['onTagsChange'];
+    isLoading?: boolean;
+    /**
+     * When true (default), pins the toolbar at the top with the same negative-margin
+     * bleed used by `DevicesPanel` (so the search row's background covers the
+     * `PageLayout` padding). Pass `false` when mounting inside a container that
+     * shouldn't bleed (e.g. a modal).
+     */
+    sticky?: boolean;
+    /**
+     * Attach to the pinned row so a caller can measure it, its height is what the
+     * sticky table header parks below, and it CHANGES as the tag-chip row appears
+     * and collapses. See `useStickyToolbar`.
+     */
+    toolbarRef?: Ref<HTMLDivElement>;
+}
+/**
+ * Search bar + "Device Tags" button + FilterModal. Pure presentation ,
+ * all state (search value, modal open/close, filter options) is owned by
+ * the parent. Reused by `DevicesPanel` and (eventually) `DeviceSelector`.
+ */
+export declare function DevicesFilterToolbar({ searchValue, onSearchChange, tags, onTagRemove, onClearAll, onSubmit, onOpenFilterModal, isFilterModalOpen, onCloseFilterModal, filterGroups, onFilterChange, currentFilters, tagFilterKeys, selectedTags, onTagsChange, isLoading, sticky, toolbarRef, }: DevicesFilterToolbarProps): import("react").JSX.Element;
+export {};
+//# sourceMappingURL=devices-filter-toolbar.d.ts.map

package/dist/components/features/devices/devices-filter-toolbar.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-filter-toolbar.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-filter-toolbar.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,cAAc,EAAE,GAAG,EAAE,MAAM,OAAO,CAAC;AAEjD,OAAO,EAAE,WAAW,EAAkB,KAAK,eAAe,EAAE,MAAM,UAAU,CAAC;AAG7E,KAAK,gBAAgB,GAAG,cAAc,CAAC,OAAO,WAAW,CAAC,CAAC;AAE3D,MAAM,WAAW,yBAAyB;IACxC,2EAA2E;IAC3E,WAAW,EAAE,MAAM,CAAC;IACpB,cAAc,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IACxC,mEAAmE;IACnE,IAAI,EAAE,eAAe,CAAC,MAAM,CAAC,EAAE,CAAC;IAChC,WAAW,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IACrC,UAAU,EAAE,MAAM,IAAI,CAAC;IACvB,QAAQ,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IAElC,kCAAkC;IAClC,iBAAiB,EAAE,MAAM,IAAI,CAAC;IAE9B,mDAAmD;IACnD,iBAAiB,EAAE,OAAO,CAAC;IAC3B,kBAAkB,EAAE,MAAM,IAAI,CAAC;IAC/B,YAAY,EAAE,gBAAgB,CAAC,cAAc,CAAC,CAAC;IAC/C,cAAc,EAAE,gBAAgB,CAAC,gBAAgB,CAAC,CAAC;IACnD,cAAc,CAAC,EAAE,gBAAgB,CAAC,gBAAgB,CAAC,CAAC;IACpD,aAAa,EAAE,gBAAgB,CAAC,eAAe,CAAC,CAAC;IACjD,YAAY,EAAE,gBAAgB,CAAC,cAAc,CAAC,CAAC;IAC/C,YAAY,EAAE,gBAAgB,CAAC,cAAc,CAAC,CAAC;IAC/C,SAAS,CAAC,EAAE,OAAO,CAAC;IAEpB;;;;;OAKG;IACH,MAAM,CAAC,EAAE,OAAO,CAAC;IAEjB;;;;OAIG;IACH,UAAU,CAAC,EAAE,GAAG,CAAC,cAAc,CAAC,CAAC;CAClC;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,EACnC,WAAW,EACX,cAAc,EACd,IAAI,EACJ,WAAW,EACX,UAAU,EACV,QAAQ,EACR,iBAAiB,EACjB,iBAAiB,EACjB,kBAAkB,EAClB,YAAY,EACZ,cAAc,EACd,cAAc,EACd,aAAa,EACb,YAAY,EACZ,YAAY,EACZ,SAAS,EACT,MAAa,EACb,UAAU,GACX,EAAE,yBAAyB,+BAwC3B"}

package/dist/components/features/devices/devices-grid-filters.d.ts

@@ -0,0 +1,25 @@
+import type { DeviceFilterColumn } from './devices-table-columns';
+export interface DevicesGridFiltersProps {
+    filterColumns: DeviceFilterColumn[];
+    /** Current filter values keyed by column id (same shape as table's tableFilters). */
+    currentFilters: Record<string, string[]>;
+    /** Called with the next filters Record on apply/reset. Should write to URL params. */
+    onFilterChange: (filters: Record<string, string[]>) => void;
+    /** Server-side count for the "N results" tail. */
+    totalCount?: number;
+    /**
+     * The facet query is still out. Keeps every filterable column in the row even
+     * though its options haven't arrived, the LABELS are static, so the row can
+     * be drawn at its real height instead of collapsing to nothing and pushing the
+     * grid down a row the moment the facets land. Used by the panel's Suspense
+     * fallback, which renders this inert.
+     */
+    isLoading?: boolean;
+}
+/**
+ * DevicesGridFilters, horizontal row of dropdown filters shown above the
+ * devices grid. Mirrors the column-header filters from the table view so the
+ * same filter set is available in both layouts.
+ */
+export declare function DevicesGridFilters({ filterColumns, currentFilters, onFilterChange, totalCount, isLoading, }: DevicesGridFiltersProps): import("react").JSX.Element | null;
+//# sourceMappingURL=devices-grid-filters.d.ts.map

package/dist/components/features/devices/devices-grid-filters.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-grid-filters.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-grid-filters.tsx"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAElE,MAAM,WAAW,uBAAuB;IACtC,aAAa,EAAE,kBAAkB,EAAE,CAAC;IACpC,qFAAqF;IACrF,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IACzC,sFAAsF;IACtF,cAAc,EAAE,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,KAAK,IAAI,CAAC;IAC5D,kDAAkD;IAClD,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB;;;;;;OAMG;IACH,SAAS,CAAC,EAAE,OAAO,CAAC;CACrB;AAED;;;;GAIG;AACH,wBAAgB,kBAAkB,CAAC,EACjC,aAAa,EACb,cAAc,EACd,cAAc,EACd,UAAU,EACV,SAAiB,GAClB,EAAE,uBAAuB,sCA8DzB"}

package/dist/components/features/devices/devices-grid.d.ts

@@ -0,0 +1,12 @@
+import type React from 'react';
+import type { DeviceRow } from './types';
+export interface DevicesGridProps<T extends DeviceRow = DeviceRow> {
+    devices: T[];
+    isLoading: boolean;
+    hasNextPage?: boolean;
+    isFetchingNextPage?: boolean;
+    sentinelRef?: React.RefObject<HTMLDivElement | null>;
+    emptyMessage?: string;
+}
+export declare function DevicesGrid<T extends DeviceRow = DeviceRow>({ devices, isLoading, hasNextPage, isFetchingNextPage, sentinelRef, emptyMessage, }: DevicesGridProps<T>): React.JSX.Element;
+//# sourceMappingURL=devices-grid.d.ts.map

package/dist/components/features/devices/devices-grid.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-grid.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-grid.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAO/B,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAEzC,MAAM,WAAW,gBAAgB,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS;IAC/D,OAAO,EAAE,CAAC,EAAE,CAAC;IACb,SAAS,EAAE,OAAO,CAAC;IACnB,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC,cAAc,GAAG,IAAI,CAAC,CAAC;IACrD,YAAY,CAAC,EAAE,MAAM,CAAC;CACvB;AAED,wBAAgB,WAAW,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAAE,EAC3D,OAAO,EACP,SAAS,EACT,WAAW,EACX,kBAAkB,EAClB,WAAW,EACX,YAAwE,GACzE,EAAE,gBAAgB,CAAC,CAAC,CAAC,qBA0DrB"}

package/dist/components/features/devices/devices-list.d.ts

@@ -0,0 +1,131 @@
+import { type ReactNode } from 'react';
+import { type NoDataProps } from '../../ui';
+import type { DeviceFilters, DeviceRow } from './types';
+/**
+ * What the user has narrowed the list down to. One shape for every surface, so a
+ * caller can keep it in the URL, in local state, or hand it straight to a server
+ * filter without translating between vocabularies.
+ */
+export interface DevicesListNarrowing {
+    search: string;
+    statuses: string[];
+    osTypes: string[];
+    organizationIds: string[];
+    /** Chips as typed. `key:value` narrows; a bare word stays visible and filters nothing. */
+    tags: string[];
+}
+export declare const EMPTY_DEVICES_NARROWING: DevicesListNarrowing;
+/** True when anything at all is narrowing the list, an empty list then means "no matches", not "nothing here". */
+export declare function isNarrowed(narrowing: DevicesListNarrowing): boolean;
+export interface DevicesListProps<T extends DeviceRow = DeviceRow> {
+    /**
+     * The rows to render, already narrowed. This component never filters and never
+     * fetches, see the module docstring.
+     */
+    devices: T[];
+    isLoading?: boolean;
+    /**
+     * Facet counts behind the column funnels and the mobile filter modal, **from
+     * the server**, the `deviceFilters` query, scoped the same way the rows are.
+     *
+     * NEVER derive these from `devices`. Counts computed off the loaded rows read
+     * as facts about the list and are not: they change with every page fetched and
+     * disagree with the server the moment anything is narrowed. A surface with no
+     * facet query of its own passes `null` (or omits this) and the table drops the
+     * funnels entirely, a control that opens onto nothing is worse than none.
+     */
+    deviceFilters?: DeviceFilters | null;
+    /**
+     * The facet query has not answered yet, keeps the funnels drawn but inert,
+     * so they don't appear out of nowhere when it does. Key it on the DATA
+     * (`!deviceFilters`), never on a react-query `isLoading`, which reads false
+     * before the request has started.
+     */
+    filtersPending?: boolean;
+    /**
+     * True while the rows on screen are the PREVIOUS result and a refetch is in
+     * flight (deferred query variables, see `useDeferredQuery`). Dims them,
+     * rather than tearing the list down to a skeleton on every keystroke.
+     */
+    isPending?: boolean;
+    /**
+     * Row count beside the column header: the server's total for the CURRENT
+     * narrowing (a connection's `filteredCount`), not the number of rows fetched
+     * so far. Honest at any point precisely because the narrowing is the server's
+     * too, a count taken from a client-side filter would contradict it.
+     */
+    totalCount?: number;
+    /** Controlled narrowing. Omit both to render a read-only list (skeletons, previews). */
+    narrowing?: DevicesListNarrowing;
+    onNarrowingChange?: (next: DevicesListNarrowing) => void;
+    /** Column ids to drop, e.g. `['organization']` when the list is already scoped to one customer. */
+    hideColumns?: string[];
+    /** Filter keys to drop from the funnels AND the modal; the column itself stays. */
+    hideFilters?: string[];
+    /** Per-row overflow menu. Omit for a read-only list. */
+    rowActions?: (device: T) => ReactNode;
+    /**
+     * Shown when the list is empty and nothing is narrowing it, the design's
+     * `data-placeholder`: icon over title over description, rendered by the
+     * table's own `DataTableEmpty`.
+     */
+    emptyState?: NoDataProps;
+    /**
+     * Shown when narrowing is what emptied it. Defaults to the table's standard
+     * "no results" state (search icon, "Try adjusting your search or filters"),
+     * which is the right answer on every list, override only to name the rows.
+     */
+    narrowedEmptyState?: NoDataProps;
+    skeletonRows?: number;
+    infiniteScroll?: {
+        hasNextPage: boolean;
+        isFetchingNextPage: boolean;
+        onLoadMore: () => void;
+        skeletonRows?: number;
+    };
+    /**
+     * Pins the search / tag toolbar to the top of the scroll area, as the fleet
+     * list does. On by default: a list long enough to scroll is exactly the one
+     * whose search must stay reachable. Turn it off only where something else is
+     * already pinned at the top.
+     */
+    stickyToolbar?: boolean;
+    /**
+     * Overrides the wrapper around the toolbar and the table. By default it adds
+     * NO gap while the toolbar is pinned, the pinned row carries its own `p-l`,
+     * and a gap on top of it doubles the space under the search box.
+     */
+    /**
+     * Where the column header parks once the rows scroll under it. Defaults to the
+     * MEASURED height of the pinned toolbar, so the two never overlap and never
+     * leave a gap, the toolbar grows and shrinks with the tag-chip row, and is
+     * shorter on a phone. Only pass this to park the header somewhere else.
+     */
+    stickyHeaderOffset?: string;
+    className?: string;
+}
+/**
+ * The devices list, search + tag chips + column funnels over the shared devices
+ * table, identical on every surface that shows devices.
+ *
+ * **It does not fetch, and it does not filter.** That is the whole point: in
+ * Relay the rows are a CONNECTION, and every surface has a different one
+ * (`devices` for the fleet, `scriptSchedule.assignedDevices` for a schedule's
+ * assignment, `availableDevices` for its picker). Baking a query in would tie
+ * the list to exactly one of them; taking `devices` + a controlled
+ * {@link DevicesListNarrowing} lets one component serve all of them.
+ *
+ * It follows that the narrowing this component reports belongs in the caller's
+ * QUERY, every devices connection takes the same `filter` / `search`, so every
+ * surface narrows server-side, over the whole list rather than the pages fetched
+ * so far. The funnel options come from the server too (`deviceFilters`), or not
+ * at all; see the `deviceFilters` prop.
+ *
+ * The rows-in / narrowing-out split is also what makes the two data layers
+ * coexist: the fleet list is still react-query over raw POST, the schedule reads
+ * Relay. When devices move to Relay, the natural next step is a colocated
+ * fragment on `Device` that each caller spreads on its own connection, the
+ * props here do not change.
+ */
+export declare function DevicesList<T extends DeviceRow = DeviceRow>({ devices, isLoading, deviceFilters, filtersPending, isPending, totalCount, narrowing, onNarrowingChange, hideColumns, hideFilters, rowActions, emptyState, narrowedEmptyState, skeletonRows, infiniteScroll, stickyToolbar, stickyHeaderOffset, className, }: DevicesListProps<T>): import("react").JSX.Element;
+//# sourceMappingURL=devices-list.d.ts.map

package/dist/components/features/devices/devices-list.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-list.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-list.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAE,KAAK,SAAS,EAAwB,MAAM,OAAO,CAAC;AAE7D,OAAO,EAAsC,KAAK,WAAW,EAAmB,MAAM,UAAU,CAAC;AAGjG,OAAO,KAAK,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAGxD;;;;GAIG;AACH,MAAM,WAAW,oBAAoB;IACnC,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,OAAO,EAAE,MAAM,EAAE,CAAC;IAClB,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B,0FAA0F;IAC1F,IAAI,EAAE,MAAM,EAAE,CAAC;CAChB;AAED,eAAO,MAAM,uBAAuB,EAAE,oBAMrC,CAAC;AAEF,kHAAkH;AAClH,wBAAgB,UAAU,CAAC,SAAS,EAAE,oBAAoB,GAAG,OAAO,CAQnE;AAED,MAAM,WAAW,gBAAgB,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS;IAC/D;;;OAGG;IACH,OAAO,EAAE,CAAC,EAAE,CAAC;IACb,SAAS,CAAC,EAAE,OAAO,CAAC;IAEpB;;;;;;;;;OASG;IACH,aAAa,CAAC,EAAE,aAAa,GAAG,IAAI,CAAC;IACrC;;;;;OAKG;IACH,cAAc,CAAC,EAAE,OAAO,CAAC;IAEzB;;;;OAIG;IACH,SAAS,CAAC,EAAE,OAAO,CAAC;IAEpB;;;;;OAKG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IAEpB,wFAAwF;IACxF,SAAS,CAAC,EAAE,oBAAoB,CAAC;IACjC,iBAAiB,CAAC,EAAE,CAAC,IAAI,EAAE,oBAAoB,KAAK,IAAI,CAAC;IAEzD,mGAAmG;IACnG,WAAW,CAAC,EAAE,MAAM,EAAE,CAAC;IACvB,mFAAmF;IACnF,WAAW,CAAC,EAAE,MAAM,EAAE,CAAC;IACvB,wDAAwD;IACxD,UAAU,CAAC,EAAE,CAAC,MAAM,EAAE,CAAC,KAAK,SAAS,CAAC;IAEtC;;;;OAIG;IACH,UAAU,CAAC,EAAE,WAAW,CAAC;IACzB;;;;OAIG;IACH,kBAAkB,CAAC,EAAE,WAAW,CAAC;IAEjC,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,cAAc,CAAC,EAAE;QACf,WAAW,EAAE,OAAO,CAAC;QACrB,kBAAkB,EAAE,OAAO,CAAC;QAC5B,UAAU,EAAE,MAAM,IAAI,CAAC;QACvB,YAAY,CAAC,EAAE,MAAM,CAAC;KACvB,CAAC;IAEF;;;;;OAKG;IACH,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB;;;;OAIG;IACH;;;;;OAKG;IACH,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAID;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAgB,WAAW,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAAE,EAC3D,OAAO,EACP,SAAS,EACT,aAAoB,EACpB,cAAc,EACd,SAAS,EACT,UAAU,EACV,SAAmC,EACnC,iBAAwB,EACxB,WAAW,EACX,WAAW,EACX,UAAU,EACV,UAAU,EACV,kBAAkB,EAClB,YAAgB,EAChB,cAAc,EACd,aAAoB,EACpB,kBAAkB,EAClB,SAAS,GACV,EAAE,gBAAgB,CAAC,CAAC,CAAC,+BA6KrB"}

package/dist/components/features/devices/devices-panel-header.d.ts

@@ -0,0 +1,46 @@
+import type { PageActionButton } from '../../ui';
+/**
+ * The panel header's contents, declared once for both the loaded panel and its
+ * `Suspense` fallback.
+ *
+ * Same reasoning as `scripts-table-columns` on the scripts pages: a loading
+ * state that RE-DECLARES the chrome it stands in for drifts from it, silently,
+ * and only in the frame nobody screenshots. Reading one declaration is what
+ * makes the two identical by construction rather than by review.
+ */
+/** The table/grid switch. Fed by the `viewMode` URL param, so it needs no data. */
+export declare const DEVICE_VIEW_MODE_ITEMS: {
+    id: string;
+    icon: import("react").JSX.Element;
+}[];
+export interface DevicePanelActionsOptions {
+    /** Shows the "Archive" button linking to the archived-devices page. */
+    archiveHref?: string;
+    showAddDevice?: boolean;
+    noOrganizations?: boolean;
+    /** Destination of the "Add Customer" button shown when the tenant has no customers. */
+    addCustomerHref?: string;
+    isCheckingOrganizations?: boolean;
+    /**
+     * Accent the "Add Device" button, the panel's pristine-empty state, which is
+     * the ONE thing here that needs the list to have answered. Left off while
+     * loading: it changes the button's colour, never its size, so the header does
+     * not move when the real answer lands.
+     */
+    accent?: boolean;
+    onAddDevice?: () => void;
+    /**
+     * Loading. Every button the loaded header will have is still rendered, same
+     * labels, same icons, same widths, but inert and without its destination, so
+     * the header is pixel-identical and nothing is clickable before the panel can
+     * honour the click.
+     */
+    disabled?: boolean;
+}
+/**
+ * The panel's header buttons. Every input is a prop or a URL value, nothing
+ * here is derived from the device query, which is what lets the fallback build
+ * the same set the loaded panel will.
+ */
+export declare function buildDevicePanelActions({ archiveHref, showAddDevice, noOrganizations, addCustomerHref, isCheckingOrganizations, accent, onAddDevice, disabled, }: DevicePanelActionsOptions): PageActionButton[];
+//# sourceMappingURL=devices-panel-header.d.ts.map

package/dist/components/features/devices/devices-panel-header.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-panel-header.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-panel-header.tsx"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,UAAU,CAAC;AAEjD;;;;;;;;GAQG;AAEH,mFAAmF;AACnF,eAAO,MAAM,sBAAsB;;;GAGlC,CAAC;AAEF,MAAM,WAAW,yBAAyB;IACxC,uEAAuE;IACvE,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,uFAAuF;IACvF,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,uBAAuB,CAAC,EAAE,OAAO,CAAC;IAClC;;;;;OAKG;IACH,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,WAAW,CAAC,EAAE,MAAM,IAAI,CAAC;IACzB;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAED;;;;GAIG;AACH,wBAAgB,uBAAuB,CAAC,EACtC,WAAW,EACX,aAAoB,EACpB,eAAuB,EACvB,eAAe,EACf,uBAA+B,EAC/B,MAAc,EACd,WAAW,EACX,QAAgB,GACjB,EAAE,yBAAyB,GAAG,gBAAgB,EAAE,CAoChD"}

package/dist/components/features/devices/devices-panel-view.d.ts

@@ -0,0 +1,79 @@
+import type { ReactNode, RefObject } from 'react';
+import { type ColumnDef, type ColumnFiltersState, type OnChangeFn, type PageActionButton } from '../../ui';
+import { type DevicesFilterToolbarProps } from './devices-filter-toolbar';
+import { type DeviceFilterColumn } from './devices-table-columns';
+import type { DeviceFilters, DeviceRow } from './types';
+export type DevicesViewMode = 'table' | 'grid';
+/** A toolbar with nothing in it and nothing wired: what a loading panel and a picture draw. */
+export declare const IDLE_DEVICES_TOOLBAR: DevicesFilterToolbarProps;
+export interface DevicesPanelViewProps<T extends DeviceRow = DeviceRow> {
+    /** Page title shown in the PageLayout header. */
+    title?: string;
+    /** Back button rendered above the title (e.g. on the archive page). */
+    backButton?: {
+        label?: string;
+        onClick: () => void;
+    };
+    /** The PageLayout wrapper's className, already resolved by the caller. */
+    className?: string;
+    /**
+     * Drawn in place of the panel's own header (title, view switch, actions),
+     * for a host that brings its own, such as a page hero.
+     */
+    headerSlot?: ReactNode;
+    viewMode: DevicesViewMode;
+    onViewModeChange?: (mode: DevicesViewMode) => void;
+    /** Header buttons: see `buildDevicePanelActions`. */
+    actions?: PageActionButton[];
+    /** The rows to draw, already narrowed. The view never fetches and never filters. */
+    devices: T[];
+    /**
+     * The request has not answered: the header, the view switch and the toolbar
+     * are the real ones, locked, and only the rows are skeletons.
+     */
+    loading?: boolean;
+    /** The rows on screen answer the previous narrowing while the next loads: dimmed, not replaced. */
+    isNarrowing?: boolean;
+    /** Server-side total for the current narrowing. */
+    totalCount?: number;
+    /** Facets behind the column funnels and the grid's filter row, from the server. */
+    deviceFilters?: DeviceFilters | null;
+    /** The filter columns the grid row offers. Defaults to every column of `deviceFilters` not in `hideFilters`. */
+    filterColumns?: DeviceFilterColumn[];
+    /** Search box, tag chips and the tags modal. Omit for an idle toolbar. */
+    toolbar?: DevicesFilterToolbarProps;
+    /** The table's column funnels. */
+    columnFilters?: ColumnFiltersState;
+    onColumnFiltersChange?: OnChangeFn<ColumnFiltersState>;
+    /** The grid filter row's selection, keyed by column id, and its writer. */
+    gridFilters?: Record<string, string[]>;
+    onGridFiltersChange?: (filters: Record<string, string[]>) => void;
+    /** The row-actions column: see `getDeviceActionsColumn`. */
+    actionsColumn?: ColumnDef<T>;
+    /** Column ids to drop from the table (e.g. 'organization' when scoped to one customer). */
+    hideColumns?: string[];
+    /** Filter keys to drop from the funnels and the grid row; the column itself stays. */
+    hideFilters?: string[];
+    /** Message shown when the list is empty. */
+    emptyMessage?: string;
+    /** Drawn instead of the toolbar and the list: the pristine, genuinely empty panel. */
+    emptyState?: ReactNode;
+    /** The tenant has no customers yet: a banner says a device needs one. */
+    noOrganizations?: boolean;
+    hasNextPage?: boolean;
+    isFetchingNextPage?: boolean;
+    onLoadMore?: () => void;
+    /** The grid's infinite-scroll sentinel. */
+    gridSentinelRef?: RefObject<HTMLDivElement | null>;
+}
+/**
+ * The device list as a page: header with the table / grid switch and the
+ * actions, the search and tag toolbar, and the rows as a table or as cards.
+ *
+ * Everything it shows is a prop. The product's container owns the queries and
+ * the URL state and maps them here; a fixture passes plain rows. Its loading
+ * state is the same component with `loading`: the chrome is the real one,
+ * locked, so the page does not move when the rows land.
+ */
+export declare function DevicesPanelView<T extends DeviceRow = DeviceRow>({ title, backButton, className, headerSlot, viewMode, onViewModeChange, actions, devices, loading, isNarrowing, totalCount, deviceFilters, filterColumns, toolbar, columnFilters, onColumnFiltersChange, gridFilters, onGridFiltersChange, actionsColumn, hideColumns, hideFilters, emptyMessage, emptyState, noOrganizations, hasNextPage, isFetchingNextPage, onLoadMore, gridSentinelRef, }: DevicesPanelViewProps<T>): import("react").JSX.Element;
+//# sourceMappingURL=devices-panel-view.d.ts.map

package/dist/components/features/devices/devices-panel-view.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devices-panel-view.d.ts","sourceRoot":"","sources":["../../../../src/components/features/devices/devices-panel-view.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,MAAM,OAAO,CAAC;AAGlD,OAAO,EAEL,KAAK,SAAS,EACd,KAAK,kBAAkB,EAEvB,KAAK,UAAU,EACf,KAAK,gBAAgB,EAGtB,MAAM,UAAU,CAAC;AAClB,OAAO,EAAwB,KAAK,yBAAyB,EAAE,MAAM,0BAA0B,CAAC;AAIhG,OAAO,EAAoB,KAAK,kBAAkB,EAA0B,MAAM,yBAAyB,CAAC;AAC5G,OAAO,KAAK,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAExD,MAAM,MAAM,eAAe,GAAG,OAAO,GAAG,MAAM,CAAC;AAO/C,+FAA+F;AAC/F,eAAO,MAAM,oBAAoB,EAAE,yBAelC,CAAC;AAEF,MAAM,WAAW,qBAAqB,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS;IACpE,iDAAiD;IACjD,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,uEAAuE;IACvE,UAAU,CAAC,EAAE;QAAE,KAAK,CAAC,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,IAAI,CAAA;KAAE,CAAC;IACrD,0EAA0E;IAC1E,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;OAGG;IACH,UAAU,CAAC,EAAE,SAAS,CAAC;IAEvB,QAAQ,EAAE,eAAe,CAAC;IAC1B,gBAAgB,CAAC,EAAE,CAAC,IAAI,EAAE,eAAe,KAAK,IAAI,CAAC;IACnD,qDAAqD;IACrD,OAAO,CAAC,EAAE,gBAAgB,EAAE,CAAC;IAE7B,oFAAoF;IACpF,OAAO,EAAE,CAAC,EAAE,CAAC;IACb;;;OAGG;IACH,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,mGAAmG;IACnG,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,mDAAmD;IACnD,UAAU,CAAC,EAAE,MAAM,CAAC;IAEpB,mFAAmF;IACnF,aAAa,CAAC,EAAE,aAAa,GAAG,IAAI,CAAC;IACrC,gHAAgH;IAChH,aAAa,CAAC,EAAE,kBAAkB,EAAE,CAAC;IACrC,0EAA0E;IAC1E,OAAO,CAAC,EAAE,yBAAyB,CAAC;IACpC,kCAAkC;IAClC,aAAa,CAAC,EAAE,kBAAkB,CAAC;IACnC,qBAAqB,CAAC,EAAE,UAAU,CAAC,kBAAkB,CAAC,CAAC;IACvD,2EAA2E;IAC3E,WAAW,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,CAAC;IACvC,mBAAmB,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC,KAAK,IAAI,CAAC;IAElE,4DAA4D;IAC5D,aAAa,CAAC,EAAE,SAAS,CAAC,CAAC,CAAC,CAAC;IAC7B,2FAA2F;IAC3F,WAAW,CAAC,EAAE,MAAM,EAAE,CAAC;IACvB,sFAAsF;IACtF,WAAW,CAAC,EAAE,MAAM,EAAE,CAAC;IACvB,4CAA4C;IAC5C,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,sFAAsF;IACtF,UAAU,CAAC,EAAE,SAAS,CAAC;IACvB,yEAAyE;IACzE,eAAe,CAAC,EAAE,OAAO,CAAC;IAE1B,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,UAAU,CAAC,EAAE,MAAM,IAAI,CAAC;IACxB,2CAA2C;IAC3C,eAAe,CAAC,EAAE,SAAS,CAAC,cAAc,GAAG,IAAI,CAAC,CAAC;CACpD;AAED;;;;;;;;GAQG;AACH,wBAAgB,gBAAgB,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAAE,EAChE,KAAiB,EACjB,UAAU,EACV,SAAc,EACd,UAAU,EACV,QAAQ,EACR,gBAAgB,EAChB,OAAO,EACP,OAAO,EACP,OAAe,EACf,WAAmB,EACnB,UAAU,EACV,aAAoB,EACpB,aAAa,EACb,OAA8B,EAC9B,aAAa,EACb,qBAAqB,EACrB,WAAwB,EACxB,mBAA0B,EAC1B,aAAa,EACb,WAAW,EACX,WAAW,EACX,YAAwE,EACxE,UAAU,EACV,eAAuB,EACvB,WAAmB,EACnB,kBAA0B,EAC1B,UAAiB,EACjB,eAAe,GAChB,EAAE,qBAAqB,CAAC,CAAC,CAAC,+BAgH1B"}

package/dist/components/features/devices/devices-table-columns.d.ts

@@ -0,0 +1,76 @@
+import type React from 'react';
+import { type ReactNode } from 'react';
+import { type ColumnDef, type ColumnFiltersState, type NoDataProps, type OnChangeFn } from '../../ui';
+import type { DeviceFilters, DeviceRow } from './types';
+/**
+ * The row-actions column, declared here beside every other device column so the
+ * loaded table and its loading state can't disagree about the column set.
+ *
+ * `renderRowActions` is optional because a loading table has no rows to act on
+ *, omit it and the column keeps its width and alignment while drawing nothing,
+ * which is exactly what the skeleton needs. Leaving the column out instead
+ * shifted every other column, since it takes real width from them.
+ */
+export declare function getDeviceActionsColumn<T extends DeviceRow = DeviceRow>(renderRowActions?: (device: T) => React.ReactNode): ColumnDef<T>;
+export declare function getDeviceOpenColumn<T extends DeviceRow = DeviceRow>(): ColumnDef<T>;
+export interface DevicesTableBodyProps<T extends DeviceRow = DeviceRow> {
+    devices: T[];
+    isLoading?: boolean;
+    /**
+     * The empty state, as the design's `data-placeholder`: icon over a title over
+     * a description. Wins over `emptyMessage` when both are given.
+     */
+    emptyState?: NoDataProps;
+    /** @deprecated Single-line variant of {@link emptyState}, pass `emptyState` instead. */
+    emptyMessage?: string;
+    skeletonRows?: number;
+    stickyHeaderOffset?: string;
+    footerSlot?: ReactNode;
+    deviceFilters?: DeviceFilters | null;
+    columnFilters?: ColumnFiltersState;
+    onColumnFiltersChange?: OnChangeFn<ColumnFiltersState>;
+    /** Optional extra column inserted before the open-in-new-tab column (e.g. row actions on the dedicated page). */
+    actionsColumn?: ColumnDef<T>;
+    /** Column ids to drop from the base table columns (e.g. ['organization'] when scoped to a single org). */
+    hideColumns?: string[];
+    /** Column ids whose header filter is dropped while the column stays visible (e.g. ['status'] on the archive page). */
+    disableColumnFilters?: string[];
+    /** The facet query is still in flight, see `getDeviceTableColumns`. */
+    filtersPending?: boolean;
+    /** Server-side total (for paginated lists). Falls back to loaded-row count when omitted. */
+    totalCount?: number;
+    /**
+     * Render the column header. Default true.
+     *
+     * Pass `false` to drop it over a genuinely empty list, column labels above
+     * nothing are noise, and the empty message reads better without a row of
+     * headings it does not explain. Keep it `true` while loading (the skeleton
+     * rows are the content it belongs to) and whenever the emptiness is the RESULT
+     * of narrowing: the column funnels live in this header, so removing it would
+     * strip the only way to undo the filter that emptied the table.
+     */
+    showHeader?: boolean;
+}
+export declare function DevicesTableBody<T extends DeviceRow = DeviceRow>({ devices, isLoading, emptyState, emptyMessage, skeletonRows, stickyHeaderOffset, footerSlot, deviceFilters, columnFilters, onColumnFiltersChange, actionsColumn, hideColumns, disableColumnFilters, filtersPending, totalCount, showHeader, }: DevicesTableBodyProps<T>): React.JSX.Element;
+export interface DeviceFilterColumn {
+    key: string;
+    label: string;
+    filterable?: boolean;
+    filterOptions?: DeviceFilterOption[];
+}
+/** A device filter dropdown entry: `meta.filter.options` plus the facet count. */
+export interface DeviceFilterOption {
+    id: string;
+    label: string;
+    value: string;
+    count?: number;
+}
+export declare function getDeviceFilterColumns(deviceFilters?: DeviceFilters | null): DeviceFilterColumn[];
+/**
+ * @param filtersPending The `deviceFilters` query is in flight, keeps the
+ * funnels drawn (inert) rather than growing them when it answers. Absent means
+ * these are the final options: an empty one then hides its funnel, which is what
+ * a list with no facet source of its own wants.
+ */
+export declare function getDeviceTableColumns<T extends DeviceRow = DeviceRow>(deviceFilters?: DeviceFilters | null, filtersPending?: boolean): ColumnDef<T>[];
+//# sourceMappingURL=devices-table-columns.d.ts.map