import "./option_list.css";
import { type FieldOptionsSource } from "./option_picker";
import type { SelectOption } from "./select";
import { type OptionListBodyProps, type OptionListModelParams } from "./option_list_body";
export interface OptionListProps<T extends string = string, MULTI extends boolean = false, D = unknown> extends Omit<OptionListModelParams<T, MULTI, D>, "options">, OptionListBodyProps<T, D> {
    /** The rows to offer. A field's own set is {@link OptionListProps.fieldOptions}. */
    options?: (SelectOption<T, D> | undefined | false)[];
    /** A SELECT FIELD, straight from the SDK (`useFieldOptions().fields.<column>`) —
     *  its whole option set becomes this picker's options, keys and colours intact.
     *  `options` wins where both are stated. */
    fieldOptions?: FieldOptionsSource<T>;
    /** DRAW EACH OF THE FIELD'S OPTIONS AS ITS OWN MARK — `dot` in a list of
     *  choices, `tonal` for the one prominent status of a surface. */
    badge?: "tonal" | "dot";
}
/**
 * The kit's option listbox body — the popover content every selector opens: a
 * Base UI `Combobox` rendered `inline`, so the keyboard model, the highlight,
 * the typeahead and the filtering are Base UI's, with single/multi selection +
 * select-all, an optional "create" row, and either a hidden capture input
 * (`search.mode:"none"`) or its own visible search field (`"internal"`).
 *
 * `Select` renders the same rows in its own popup; the chat composer and the
 * in-cell editors host this one directly. Don't hand-roll a search-list — reach
 * for this.
 */
export declare function OptionList<T extends string, MULTI extends boolean = false, D = unknown>(props: OptionListProps<T, MULTI, D>): import("react").JSX.Element;