cekat-ui 1.3.17 → 1.3.18

package/dist/index.d.mts

@@ -1673,6 +1673,30 @@ export { SelectionIndicator }
  */
 export declare function SelectItem<T extends object>({ className, ...props }: ListBoxItemProps<T>): JSX_2.Element;
 
+/**
+ * `Popover` + `ListBox`, with a search field filtering `items` in between. The query is read
+ * from `useSelectSearchContext` rather than local state — see `select.context.ts` for why.
+ */
+export declare function SelectPopover<T extends object>({ items, children, getTextValue, filter, searchPlaceholder, searchAriaLabel, emptyState, className, }: SelectPopoverProps<T>): JSX_2.Element;
+
+/**
+ * Drop-in replacement for a plain `Popover` + `ListBox` pair (see `Calendar.tsx` for that bare
+ * composition) that adds a search field above the list, filtering `items` client-side — the
+ * same shape as `MultiSelectPopover`, adapted for `Select`'s single-value case. The query itself
+ * lives in `Select`, not here — see `select.context.ts`.
+ */
+export declare interface SelectPopoverProps<T extends object> {
+    items: Iterable<T>;
+    children: (item: T) => React_2.ReactElement;
+    getTextValue: (item: T) => string;
+    filter?: (item: T, query: string) => boolean;
+    searchPlaceholder?: string;
+    /** `aria-label` on the search field — it has no visible label. Default `'Search options'`. */
+    searchAriaLabel?: string;
+    emptyState?: React_2.ReactNode;
+    className?: ClassValue;
+}
+
 /**
  * Single-value by construction — RAC's `Select` also supports `selectionMode: 'multiple'`,
  * deliberately not exposed here. A multi-value trigger is a different interaction (chips, no

package/dist/index.d.ts

@@ -1673,6 +1673,30 @@ export { SelectionIndicator }
  */
 export declare function SelectItem<T extends object>({ className, ...props }: ListBoxItemProps<T>): JSX_2.Element;
 
+/**
+ * `Popover` + `ListBox`, with a search field filtering `items` in between. The query is read
+ * from `useSelectSearchContext` rather than local state — see `select.context.ts` for why.
+ */
+export declare function SelectPopover<T extends object>({ items, children, getTextValue, filter, searchPlaceholder, searchAriaLabel, emptyState, className, }: SelectPopoverProps<T>): JSX_2.Element;
+
+/**
+ * Drop-in replacement for a plain `Popover` + `ListBox` pair (see `Calendar.tsx` for that bare
+ * composition) that adds a search field above the list, filtering `items` client-side — the
+ * same shape as `MultiSelectPopover`, adapted for `Select`'s single-value case. The query itself
+ * lives in `Select`, not here — see `select.context.ts`.
+ */
+export declare interface SelectPopoverProps<T extends object> {
+    items: Iterable<T>;
+    children: (item: T) => React_2.ReactElement;
+    getTextValue: (item: T) => string;
+    filter?: (item: T, query: string) => boolean;
+    searchPlaceholder?: string;
+    /** `aria-label` on the search field — it has no visible label. Default `'Search options'`. */
+    searchAriaLabel?: string;
+    emptyState?: React_2.ReactNode;
+    className?: ClassValue;
+}
+
 /**
  * Single-value by construction — RAC's `Select` also supports `selectionMode: 'multiple'`,
  * deliberately not exposed here. A multi-value trigger is a different interaction (chips, no