@dloizides/ui-forms 1.7.0 → 1.9.0

package/dist/index.d.ts

@@ -1,5 +1,47 @@
 import React from 'react';
-import { StyleProp, TextStyle, ViewStyle, TextInputProps, TextInput } from 'react-native';
+import { StyleProp, TextStyle, ViewStyle, TextInputProps, TextInput, View } from 'react-native';
+
+/**
+ * `Field`'s TWO spacing models — the F3 fix, shipped as an OPT-IN rather than a breaking change.
+ *
+ * ## The defect
+ *
+ * `Field` hard-coded a 16px bottom margin on its container and 4px margins on its label / hint /
+ * error. That is the pre-flexbox model: the CHILD owns the space after itself. In a `gap`-laid-out
+ * parent — which is how every modern form row in this fleet is written — the child's margin STACKS
+ * on the parent's gap, so the consumer has to cancel it by hand. aml-v2 alone carries 13
+ * `marginBottom: 0` cancels, each with an apologetic comment; the fleet carries 16.
+ *
+ * AML v1 got this right in CSS: `.ui-field { display: flex; flex-direction: column; gap: 6px; }` —
+ * internal gap only, and the parent grid owns the space BETWEEN fields. That contract is written up
+ * in `PROOViD/AMLService/AMLService/wwwroot/shared/FORMS.md` ("The gap is owned by the container,
+ * never by margins on the children").
+ *
+ * ## Why opt-in and not a 2.0.0
+ *
+ * Switching every `Field` to the gap model at once moves pixels on every form in seven portals in a
+ * single publish — which is exactly the change you cannot visually QA, because there is no app you
+ * can look at that is still on the old behaviour to compare against. The two models are therefore
+ * both implemented, selected per field:
+ *
+ *  - `stack` (DEFAULT) — the historical margins, byte-identical to 1.8.0. Every existing consumer
+ *    is untouched, including the 16 that currently cancel the margin.
+ *  - `gap` — the FORMS.md contract: no bottom margin at all, uniform 6px internal gap. The parent
+ *    owns the rhythm.
+ *
+ * A `Field` inside a `FormGrid` resolves to `gap` automatically, so adopting the shared grid IS the
+ * opt-in — the consumer deletes its hand-rolled `grid`/`field` styles and its margin cancel in the
+ * same edit, and the fleet migrates one app at a time behind visual QA.
+ */
+
+/**
+ * Which spacing model a field speaks.
+ *
+ * A plain string union rather than a `const enum` for the same reason as `FieldLabelVariant`: this
+ * type crosses the package boundary into consumers' `.d.ts`, and a cross-boundary `const enum`
+ * breaks `isolatedModules` / Babel-only builds.
+ */
+type FieldSpacing = 'stack' | 'gap';
 
 /**
  * The TWO legitimate label voices, per the shared forms contract
@@ -102,9 +144,18 @@ interface FieldProps {
      * plus a `grow` modifier — instead of having to restate a COMPLETE style per variant.
      */
     containerStyle?: StyleProp<ViewStyle>;
+    /**
+     * Which of the two spacing models this field speaks — see `fieldSpacing.ts`.
+     *
+     * Leave it unset. Inside a `FormGrid` or `FormSection` it resolves to `gap` (the FORMS.md
+     * contract: no bottom margin, the parent's `gap` owns the rhythm); anywhere else it resolves to
+     * `stack` (the historical 16px margin, byte-identical to 1.8.0). Set it explicitly only to
+     * override that — e.g. a cell inside a grid that genuinely stacks two fields wants `stack`.
+     */
+    spacing?: FieldSpacing;
     testID?: string;
 }
-declare const Field: ({ label, children, required, optional, optionalLabel, hint, error, labelVariant, labelStyle, containerStyle, testID, }: FieldProps) => React.ReactElement;
+declare const Field: ({ label, children, required, optional, optionalLabel, hint, error, labelVariant, labelStyle, containerStyle, spacing, testID, }: FieldProps) => React.ReactElement;
 
 /**
  * Required / optional markers, per the shared forms contract
@@ -137,6 +188,117 @@ type FieldMarker = 'none' | 'required' | 'optional';
  */
 declare const DEFAULT_OPTIONAL_LABEL = "(optional)";
 
+/**
+ * `FormGrid` — the wrapping form row, extracted from ~177 hand-rolled copies.
+ *
+ * Verbatim in every portal, differing only in one constant:
+ *
+ * ```ts
+ * grid:  { flexDirection: 'row', flexWrap: 'wrap', gap: 12 },
+ * field: { minWidth: 220, flexGrow: 1, flexBasis: 260 },   // or 200/240/260
+ * ```
+ *
+ * Extracting it is worth more than the deleted lines: because the grid declares itself through
+ * `FormGridContext`, a `Field` inside it knows its vertical rhythm is owned by the grid's `gap` and
+ * drops its own bottom margin. That kills the fleet's 16 `marginBottom: 0` cancel hacks at the same
+ * time — the grid and the cancel were always two halves of one bug.
+ *
+ * The cell metrics live on the GRID, not on each cell, because that is how the real call sites are
+ * written: one `styles.field` reused by every cell in the row, with the occasional narrow one-off.
+ * `<FormCell>` with no props is therefore the common case, and `<FormCell basis={160} grow={false}>`
+ * the exception — which is exactly the ratio in aml-v2's `ScreeningForm`.
+ */
+
+interface FormGridProps {
+    children: React.ReactNode;
+    /**
+     * Space between cells, horizontally AND between wrapped rows. This is the value that makes the
+     * grid own the vertical rhythm, so it is also what a descendant `Field` is dropping its own
+     * margin in favour of.
+     */
+    gap?: number;
+    /** Default `minWidth` for every `FormCell` in this grid. */
+    minWidth?: number;
+    /** Default `flexBasis` for every `FormCell` in this grid. */
+    basis?: number;
+    style?: StyleProp<ViewStyle>;
+    testID?: string;
+}
+declare const FormGrid: ({ children, gap, minWidth, basis, style, testID, }: FormGridProps) => React.ReactElement;
+
+/**
+ * `FormCell` — one cell of a `FormGrid`.
+ *
+ * Replaces the `<View style={styles.field}>` wrapper every real call site already puts around each
+ * control. It inherits `minWidth` / `flexBasis` from the enclosing grid so the common case is a bare
+ * `<FormCell>`, and takes per-cell overrides for the genuine one-offs (aml-v2's `fieldNarrow`:
+ * `minWidth: 140, flexBasis: 160, flexGrow: 0`).
+ *
+ * Used OUTSIDE a `FormGrid` it still renders a sensible cell from the package defaults rather than
+ * throwing — a cell is a layout hint, and a form that renders slightly wide is a better failure than
+ * a form that does not render. The grid-owned SPACING behaviour, by contrast, is deliberately NOT
+ * available this way: that one has to come from a real grid, because a `Field` dropping its margin
+ * with nothing to replace it would collapse the form.
+ */
+
+interface FormCellProps {
+    children: React.ReactNode;
+    /** Overrides the grid's `minWidth` for this cell only. */
+    minWidth?: number;
+    /** Overrides the grid's `basis` for this cell only. */
+    basis?: number;
+    /** `false` pins the cell to its basis instead of letting it absorb the row's slack. */
+    grow?: boolean;
+    style?: StyleProp<ViewStyle>;
+    testID?: string;
+}
+declare const FormCell: ({ children, minWidth, basis, grow, style, testID, }: FormCellProps) => React.ReactElement;
+
+/**
+ * `FormSection` — a titled group of fields. The React answer to v1's `<fieldset>` / `<legend>`.
+ *
+ * v1 has a real `<fieldset>` whose `<legend>` takes the identical label metric as a field label, so
+ * a group heading reads as part of the form rather than as page furniture. Nothing in the React
+ * fleet has this: zygos fakes it with a generic `Heading`, and everybody else emits an untitled
+ * `<View>` — which means the grouping exists visually but not semantically, so a screen-reader user
+ * tabbing into "Threshold" is never told it belongs to "Advanced matching".
+ *
+ * ## Why not a literal `<fieldset>`
+ *
+ * react-native-web has no `fieldset` mapping — a `View` is a `div`, and there is no escape hatch
+ * that turns one into a `<fieldset>` with a real `<legend>`. What IS available is the pattern the
+ * ARIA spec defines as the equivalent: `role="group"` + `aria-labelledby` pointing at the heading.
+ * Assistive tech announces "Advanced matching, group" exactly as it would for a fieldset. This is
+ * the honest ceiling of the platform, not a shortcut — and it is why the legend is a `Text` whose
+ * `nativeID` is generated the same way `Field`'s hint/error ids are.
+ *
+ * The legend deliberately reuses `resolveLabelVariantStyle` — the SAME function `Field` uses for its
+ * label — so the two cannot drift. A section titled in one metric above fields labelled in another
+ * is precisely the "third voice is drift" failure FORMS.md warns about.
+ */
+
+interface FormSectionProps {
+    /**
+     * The legend — pre-localized, like every string in this package. Optional: a section with no
+     * title still groups its children for layout, but renders NO legend row and NO `aria-labelledby`,
+     * because a group labelled by an empty element is worse for assistive tech than an unlabelled one.
+     */
+    title?: string;
+    /** Help line for the whole group, under the legend. The group-level sibling of `Field`'s hint. */
+    description?: string;
+    children: React.ReactNode;
+    /**
+     * Which label voice the legend speaks. Defaults to `field` — a section heading on a form the user
+     * fills in. Pass `control` on a dense surface so the legend matches the controls beneath it.
+     */
+    labelVariant?: FieldLabelVariant;
+    /** Escape hatch applied AFTER `labelVariant`, for the genuine one-off a variant does not cover. */
+    titleStyle?: StyleProp<TextStyle>;
+    style?: StyleProp<ViewStyle>;
+    testID?: string;
+}
+declare const FormSection: ({ title, description, children, labelVariant, titleStyle, style, testID, }: FormSectionProps) => React.ReactElement;
+
 /**
  * `FormActions` — the submit/cancel button row every form ends with.
  *
@@ -289,7 +451,17 @@ interface ChipSelectorProps<T> {
     disabled?: boolean;
     /** Visual variant. `solid` (default) = filled selected pill; `outline` = v1 tinted-outline. */
     variant?: ChipVariant;
-    containerStyle?: ViewStyle;
+    /**
+     * `StyleProp` (not a bare `ViewStyle`) so it composes the same way `Field`'s does — a caller can
+     * pass an array instead of restating a complete style per variant.
+     */
+    containerStyle?: StyleProp<ViewStyle>;
+    /**
+     * Forwarded verbatim to the underlying `Field`. `ChipSelector` deliberately holds NO spacing
+     * opinion of its own: it delegates, so the two cannot drift into disagreeing about how much room
+     * a chip block occupies. The guard for that is `chipSelectorFieldLockstep` in the tests.
+     */
+    spacing?: FieldSpacing;
     /** Marks the selection mandatory — renders `Field`'s decorative `*` next to the label. */
     required?: boolean;
     /** Validation message under the chips, wired to the chip group via `aria-describedby`. */
@@ -308,7 +480,7 @@ interface ChipSelectorProps<T> {
      */
     optionAccessibilityHint?: string;
 }
-declare const ChipSelector: <T extends string | number>({ label, options, value, onChange, multiple, disabled, variant, containerStyle, required, error, testID, chipTestIDPrefix, optionAccessibilityHint, }: ChipSelectorProps<T>) => React.ReactElement;
+declare const ChipSelector: <T extends string | number>({ label, options, value, onChange, multiple, disabled, variant, containerStyle, spacing, required, error, testID, chipTestIDPrefix, optionAccessibilityHint, }: ChipSelectorProps<T>) => React.ReactElement;
 
 /**
  * Reusable form switch/toggle with an optional description.
@@ -351,4 +523,277 @@ interface FormCheckboxProps {
 }
 declare const FormCheckbox: ({ label, value, onValueChange, onChange, hint, description, disabled, containerStyle, testID, accessibilityLabel, accessibilityHint, }: FormCheckboxProps) => React.ReactElement;
 
-export { type ChipOption, ChipSelector, type ChipSelectorProps, type ChipVariant, DEFAULT_OPTIONAL_LABEL, Field, type FieldChildContext, type FieldChildren, type FieldLabelVariant, type FieldMarker, type FieldProps, FormActions, type FormActionsProps, FormCheckbox, type FormCheckboxProps, FormField, type FormFieldProps, FormSwitch, type FormSwitchProps, type ThemedInput, ThemedTextInput, type ThemedTextInputProps, type UseThemedInputOptions, useThemedInput };
+/**
+ * Shared value types for the dense CONTROLS (select / typeahead / date-range) promoted out of
+ * `@dloizides/ui-tables`' private filter bar.
+ *
+ * They live here, not in `ui-tables`, because a control's option list and a date range are form
+ * concepts — a filter bar is only one surface that happens to compose them. `ui-tables` aliases
+ * its long-standing public names (`FilterOption`, `DateRangeValue`) onto these, so there is ONE
+ * definition and the two can never drift into structurally-compatible-but-separate twins.
+ */
+/** A single choice in a select / typeahead. `label` is PRE-LOCALIZED by the caller. */
+interface ControlOption {
+    readonly label: string;
+    readonly value: string;
+}
+/** The inclusive from/to value of a date-range control (each an ISO `YYYY-MM-DD` string, or ''). */
+interface DateRangeValue {
+    readonly from: string;
+    readonly to: string;
+}
+
+/**
+ * `SelectControl` — a single-select enum/status dropdown. A bordered trigger shows the selected
+ * option's label (or the placeholder when unset) plus a chevron; pressing it opens the shared
+ * {@link AnchoredMenu}. Selecting fires `onChange` and closes.
+ *
+ * Promoted out of `@dloizides/ui-tables`' private `Filters/fields/SelectField`, where six portals
+ * could see it working and none could import it — which is why the fleet grew SIX independent
+ * select implementations.
+ *
+ * The control is LABEL-FREE by design: wrap it in a `Field` (with `labelVariant="control"` on a
+ * dense surface) to get the label, hint and error slots. That keeps one label implementation for
+ * every control instead of one per control.
+ *
+ * i18n: this package never calls `t`. `accessibilityLabel`, `placeholder`, `accessibilityHint`
+ * and `optionHint` are PRE-LOCALIZED strings supplied by the caller — the only shape that can
+ * serve both aml-v2's positional `{0}` `@dloizides/i18n` and the other six portals' i18next
+ * `{{p1}}` from one component.
+ */
+
+interface SelectControlProps {
+    options: readonly ControlOption[];
+    /** The selected option's `value`. `''` (or any unmatched value) renders the placeholder. */
+    value: string;
+    onChange: (value: string) => void;
+    /** PRE-LOCALIZED text shown when the value matches no option. */
+    placeholder?: string;
+    /**
+     * PRE-LOCALIZED accessible NAME of the trigger. It REPLACES the trigger's visible text for a
+     * screen reader, so it must carry the SELECTION too — "Status: Active", not just "Status",
+     * which announces the control but silently hides its value.
+     */
+    accessibilityLabel: string;
+    accessibilityHint?: string;
+    /** PRE-LOCALIZED accessibility hint applied to every option in the menu. */
+    optionHint?: string;
+    /** Merged LAST onto the anchor wrapper — the consumer always wins over the shared style. */
+    style?: StyleProp<ViewStyle>;
+    /** Trigger is `${testID}-trigger`, menu `${testID}-menu`, options `${testID}-option-${value}`. */
+    testID: string;
+}
+declare function SelectControl({ options, value, onChange, placeholder, accessibilityLabel, accessibilityHint, optionHint, style, testID, }: SelectControlProps): React.ReactElement;
+
+/**
+ * `TypeaheadControl` — a search-as-you-type combobox (aml-v2's CountryPicker, generalized). A
+ * text input plus a floating {@link AnchoredMenu} of ranked suggestions ({@link suggestOptions});
+ * picking one fills the canonical label.
+ *
+ * Free typing is PRESERVED: the value is the raw text, so a caller can accept "CY", "cyprus" or
+ * "Cyprus (CY)" and normalise it themselves at query time, exactly as aml does. An optional
+ * PRE-LOCALIZED `error` shows a persistent banner and tints the border.
+ *
+ * Promoted out of `@dloizides/ui-tables`' private `Filters/fields/TypeaheadField`.
+ *
+ * Label-free by design — wrap in a `Field` for the label/hint slots.
+ */
+
+/** Default min characters before suggestions surface. */
+declare const DEFAULT_TYPEAHEAD_MIN_CHARS = 1;
+/** Default cap on rendered suggestions. */
+declare const DEFAULT_TYPEAHEAD_MAX_SUGGESTIONS = 8;
+interface TypeaheadControlProps {
+    options: readonly ControlOption[];
+    /** The raw text in the box — NOT necessarily an option value. */
+    value: string;
+    onChange: (value: string) => void;
+    /** Called on Enter/submit (after the menu closes). Omit if the surface has nothing to commit. */
+    onSubmit?: () => void;
+    placeholder?: string;
+    /** PRE-LOCALIZED accessible name of the input. */
+    accessibilityLabel: string;
+    accessibilityHint?: string;
+    /** PRE-LOCALIZED accessibility hint applied to every suggestion. */
+    optionHint?: string;
+    /** PRE-LOCALIZED inline error (e.g. "Unrecognised country"). Shows a persistent banner. */
+    error?: string;
+    /** Minimum characters before suggestions surface. Default 1. */
+    minChars?: number;
+    /** Cap on rendered suggestions. Default 8. */
+    maxSuggestions?: number;
+    /** Merged LAST onto the anchor wrapper. */
+    style?: StyleProp<ViewStyle>;
+    /** Input is `${testID}-input`, menu `${testID}-menu`, error `${testID}-error`. */
+    testID: string;
+}
+declare function TypeaheadControl({ options, value, onChange, onSubmit, placeholder, accessibilityLabel, accessibilityHint, optionHint, error, minChars, maxSuggestions, style, testID, }: TypeaheadControlProps): React.ReactElement;
+
+/**
+ * `DateRangeControl` — an inclusive from/to pair (aml cases `from`/`to`, kefi audit `from`/`to`).
+ * Each side is a `YYYY-MM-DD` text input; on web the browser's native date UI is offered via
+ * `type="date"` (a react-native-web `TextInput` passes unknown props to the DOM input). Editing
+ * either side patches ONLY that side, so the other survives the edit.
+ *
+ * Promoted out of `@dloizides/ui-tables`' private `Filters/fields/DateRangeField`, which is why
+ * the fleet grew FIVE independent date fields.
+ *
+ * Label-free by design — the From/To sub-labels name the two HALVES; wrap in a `Field` for the
+ * range's own label.
+ */
+
+interface DateRangeControlProps {
+    value: DateRangeValue;
+    onChange: (value: DateRangeValue) => void;
+    /** Called on Enter/submit in either side. */
+    onSubmit?: () => void;
+    /** PRE-LOCALIZED sub-label for the FROM input (e.g. "From"). Also its accessible name. */
+    fromLabel: string;
+    /** PRE-LOCALIZED sub-label for the TO input (e.g. "To"). Also its accessible name. */
+    toLabel: string;
+    fromPlaceholder?: string;
+    toPlaceholder?: string;
+    /** PRE-LOCALIZED hint applied to BOTH inputs. */
+    accessibilityHint?: string;
+    /** Merged LAST onto the row wrapper. */
+    style?: StyleProp<ViewStyle>;
+    /** Row is `${testID}-range`, inputs `${testID}-from` / `${testID}-to`. */
+    testID: string;
+}
+declare function DateRangeControl({ value, onChange, onSubmit, fromLabel, toLabel, fromPlaceholder, toPlaceholder, accessibilityHint, style, testID, }: DateRangeControlProps): React.ReactElement;
+
+/**
+ * `AnchoredMenu` — the floating option list shared by `SelectControl` and `TypeaheadControl`.
+ *
+ * Renders an in-tree, absolutely-positioned popover under its anchor (the pattern aml-v2's
+ * CountryPicker proved: `position:absolute; top:100%; zIndex; elevation`), so it floats over
+ * sibling fields without a portal. On web it dismisses on outside-click / Escape; on native the
+ * caller closes it on blur/select. Purely presentational + theme-flat, so it stays reusable.
+ *
+ * Promoted verbatim out of `@dloizides/ui-tables`' private `Filters/components/AnchoredMenu`.
+ *
+ * Deliberately in-tree (no `ui-layout` dependency). That was a considered choice in `ui-tables`
+ * and it still holds here: `ui-forms` is a low-level primitive and must not take a runtime
+ * dependency on the higher-level `ui-layout` `ModalDropdown` — that would invert the graph for
+ * every consumer. Apps needing the responsive modal/bottom-sheet variant inject it instead.
+ */
+
+/** The four theme colours the menu paints with — passed in, so the menu stays theme-flat. */
+interface AnchoredMenuColors {
+    text: string;
+    border: string;
+    surface: string;
+    brand: string;
+}
+interface AnchoredMenuProps {
+    options: readonly ControlOption[];
+    /** The currently-selected value, highlighted in the list ('' = none). */
+    selectedValue: string;
+    onSelect: (value: string) => void;
+    onDismiss: () => void;
+    colors: AnchoredMenuColors;
+    /** PRE-LOCALIZED accessibility hint applied to every option. */
+    optionHint: string;
+    /** Base testID: the menu is `${testID}-menu`, each option `${testID}-option-${value}`. */
+    testID: string;
+    /** Node whose clicks count as "inside" (the anchor) so its own press doesn't self-dismiss. */
+    anchorRef: React.RefObject<View | null>;
+}
+declare function AnchoredMenu({ options, selectedValue, onSelect, onDismiss, colors, optionHint, testID, anchorRef, }: AnchoredMenuProps): React.ReactElement;
+
+declare const controlStyles: {
+    /** The shared bordered box every dense text control renders in. */
+    input: {
+        borderWidth: number;
+        borderRadius: number;
+        paddingHorizontal: number;
+        paddingVertical: number;
+        fontSize: number;
+    };
+    /** The select trigger: a bordered field box matching the text inputs + a chevron. */
+    selectTrigger: {
+        flexDirection: "row";
+        alignItems: "center";
+        justifyContent: "space-between";
+        gap: number;
+        borderWidth: number;
+        borderRadius: number;
+        paddingHorizontal: number;
+        paddingVertical: number;
+    };
+    selectTriggerText: {
+        fontSize: number;
+        flexShrink: number;
+    };
+    chevron: {
+        fontSize: number;
+    };
+    dateRow: {
+        flexDirection: "row";
+        gap: number;
+    };
+    dateCol: {
+        gap: number;
+        flex: number;
+    };
+    /**
+     * The micro-caption above a sub-control (a date range's From/To) and beside a switch. Note it
+     * is deliberately NOT the `control` label voice: it carries no `700`/uppercase, because it
+     * names a HALF of a control that already has a `control`-voice label above it. Uppercasing it
+     * too would make one field shout twice.
+     */
+    subLabel: {
+        fontSize: number;
+        letterSpacing: number;
+    };
+    /** Positioning context for a floating `AnchoredMenu` (`position:absolute; top:100%`). */
+    anchor: {
+        position: "relative";
+    };
+    menu: {
+        position: "absolute";
+        top: "100%";
+        left: number;
+        marginTop: number;
+        minWidth: number;
+        maxHeight: number;
+        borderWidth: number;
+        borderRadius: number;
+        paddingVertical: number;
+        zIndex: number;
+        boxShadow: string;
+        elevation: number;
+        overflow: "hidden";
+    };
+    option: {
+        paddingHorizontal: number;
+        paddingVertical: number;
+    };
+    optionText: {
+        fontSize: number;
+    };
+    error: {
+        fontSize: number;
+        marginTop: number;
+    };
+};
+
+/**
+ * `suggestOptions` — the ranked substring matcher behind `TypeaheadControl`, generalized from
+ * aml-v2's `suggestCountries` and promoted verbatim out of `@dloizides/ui-tables`' private
+ * `Filters/utils/suggest.ts`.
+ *
+ * Ranks: value exact (0) > value prefix (1) > label prefix (2) > label contains (3); ties broken
+ * by `label.localeCompare`. Empty/short queries return `[]` — nothing surfaces until `minChars`
+ * is typed, mirroring a native `<datalist>`.
+ */
+
+/**
+ * Rank + cap the options matching `query`. Returns `[]` until `query` (trimmed) is at least
+ * `minChars` long, then the best `limit` matches, ranked as documented above.
+ */
+declare function suggestOptions(options: readonly ControlOption[], query: string, minChars: number, limit: number): readonly ControlOption[];
+/** True when `text` is non-empty yet matches no option's value or label exactly (case-insensitive). */
+declare function isUnmatched(options: readonly ControlOption[], text: string): boolean;
+
+export { AnchoredMenu, type AnchoredMenuColors, type AnchoredMenuProps, type ChipOption, ChipSelector, type ChipSelectorProps, type ChipVariant, type ControlOption, DEFAULT_OPTIONAL_LABEL, DEFAULT_TYPEAHEAD_MAX_SUGGESTIONS, DEFAULT_TYPEAHEAD_MIN_CHARS, DateRangeControl, type DateRangeControlProps, type DateRangeValue, Field, type FieldChildContext, type FieldChildren, type FieldLabelVariant, type FieldMarker, type FieldProps, type FieldSpacing, FormActions, type FormActionsProps, FormCell, type FormCellProps, FormCheckbox, type FormCheckboxProps, FormField, type FormFieldProps, FormGrid, type FormGridProps, FormSection, type FormSectionProps, FormSwitch, type FormSwitchProps, SelectControl, type SelectControlProps, type ThemedInput, ThemedTextInput, type ThemedTextInputProps, TypeaheadControl, type TypeaheadControlProps, type UseThemedInputOptions, controlStyles, isUnmatched, suggestOptions, useThemedInput };