import React from "react";
import { type FieldOption, type OptionValue } from "./status";
import type { SelectOption } from "./select";
/** A SELECT FIELD'S OWN OPTIONS, as the SDK hands them over — the complete set
 *  with its colours, including options no current row carries. Structural rather
 *  than imported, because the kit may not depend on `@lotics/app-sdk`. */
export interface FieldOptionsSource<T extends string = string> {
    options: readonly FieldOption<T>[];
}
/** THE FIELD AS A PICKER'S OPTIONS — and, where the caller asked for the BADGE,
 *  each row drawn as the option's own mark. The colour is resolved by KEY rather
 *  than carried in `data`, so a picker generic over its payload keeps it. */
export declare function fieldPicker<T extends string, D = unknown>(field: FieldOptionsSource<T>, badge?: "tonal" | "dot"): {
    options: SelectOption<T, D>[];
    renderOptionContent?: (option: SelectOption<T, D>) => React.ReactNode;
};
/**
 * Feed a select FIELD's options into any kit picker without dropping what the
 * field knows — a picker takes `{ value, label }`, and the option's `color` is
 * not in that shape.
 *
 *     <Select {...optionPicker(fields.city?.options ?? [])} … />                    // a category
 *     <Select {...optionPicker(fields.status?.options ?? [], { badge: "dot" })} … /> // a status
 *
 * **`badge` is OPT-IN.** A badge means STATUS; a type, a category or a count is
 * not one and renders as plain text. `dot` over `tonal` when you do badge: a
 * stack of filled pills is heavier than the list describing them.
 */
export declare function optionPicker(options: OptionValue[], opts?: {
    badge?: "tonal" | "dot";
}): {
    options: SelectOption<string, OptionValue>[];
    renderOptionContent?: (option: SelectOption<string, OptionValue>) => React.ReactNode;
};