import { Field as BaseField } from '@base-ui/react/field';
import { Fieldset as BaseFieldset } from '@base-ui/react/fieldset';
import * as React from 'react';
/**
 * A form field: a label, a control, a hint and an error, wired together.
 *
 * **This is the thing Strix was missing.** `Label`, `HelpText` and `Input` all existed, and every
 * consumer wired `id`, `aria-describedby` and `aria-invalid` between them by hand — which is the
 * kind of work that is silently skipped, leaving a field whose hint no screen reader reads.
 * `Field.Root` owns that wiring, and it is Base UI's rather than ours.
 *
 * Composes the existing `Label` and `HelpText` class lists rather than restating them, so a field's
 * label cannot drift from a standalone one.
 *
 * @example
 * <Field>
 *   <FieldLabel>Email</FieldLabel>
 *   <FieldControl render={<Input placeholder="you@example.com" />} />
 *   <FieldDescription>We never share it.</FieldDescription>
 *   <FieldError match="valueMissing">Enter an email address.</FieldError>
 * </Field>
 *
 * @example
 * // An external validator owns the decision, so `invalid` shows the message.
 * <Field invalid={Boolean(meta.error)}>
 *   <FieldLabel>Email</FieldLabel>
 *   <FieldControl render={<Input />} />
 *   <FieldError>{meta.error}</FieldError>
 * </Field>
 */
export type FieldProps = React.ComponentPropsWithoutRef<typeof BaseField.Root>;
export declare const Field: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldRootProps, "ref"> & React.RefAttributes<HTMLDivElement>, "ref"> & React.RefAttributes<HTMLDivElement>>;
export type FieldLabelProps = React.ComponentPropsWithoutRef<typeof BaseField.Label>;
/**
 * The field's label.
 *
 * `BaseField.Label` for the wiring, rendering Strix's own {@link Label} for the treatment. Base UI
 * generates the id pair, so no `htmlFor` is written by hand and none can go stale; `Label` supplies
 * the type role, so a field's label cannot drift from a standalone one.
 *
 * **IT USED TO DRIFT, AND THE DOCBLOCK HERE CLAIMED IT DID NOT.** This applied `labelStyles()` — the
 * three-class box, not the type — and then wrote its own ramp over the top:
 * `text-size-body-small font-body-small-medium`, 14px at weight 500. A standalone `Label` is
 * `body-m-semibold`, 16px at 600, and it also carries `font-sans`, which this dropped entirely, so
 * the label fell through to inherited family. Two label treatments coexisted on one form and the
 * mismatch was only visible side by side; the comment asserting they matched is why nobody looked.
 *
 * Figma says 16/24 semibold, twice: `.label` (22:3960) and `.input-dropdown` both draw the label
 * under the composite style `Paragraph/medium-semibold`, which is `font/size/small` 16px over
 * `font/line-height/small` 24px at `font/weight/Semibold` (CSS 600). `input-dropdown`'s binding
 * calls "Medium" here an error and corrects it explicitly.
 *
 * 14/Medium was not Figma's label at all — it is `Paragraph/small-medium`, which `.input-text` puts
 * on the **value inside the field**. Dev Mode names that layer `[FieldLabel]`, a bracketed
 * placeholder for the input's own text, and the name is almost certainly how it got copied onto the
 * label above the field. Composing `Label` is what stops the next such reading: there is no second
 * ramp left to write.
 */
export declare const FieldLabel: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldLabelProps, "ref"> & React.RefAttributes<HTMLElement>, "ref"> & React.RefAttributes<HTMLLabelElement>>;
export type FieldControlProps = React.ComponentPropsWithoutRef<typeof BaseField.Control>;
/**
 * The control.
 *
 * Renders a bare `<input>` by default and takes `render` for anything else —
 * `render={<Input />}`, `render={<Textarea />}`, `render={<Switch />}`. That seam is what keeps
 * `Field` from becoming a second input implementation: the styling stays in the component being
 * rendered, and `Field` contributes only the wiring.
 */
export declare const FieldControl: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldControlProps, "ref"> & React.RefAttributes<HTMLElement>, "ref"> & React.RefAttributes<HTMLInputElement>>;
export type FieldDescriptionProps = React.ComponentPropsWithoutRef<typeof BaseField.Description>;
/** A hint, linked into the control's `aria-describedby` by Base UI. */
export declare const FieldDescription: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldDescriptionProps, "ref"> & React.RefAttributes<HTMLParagraphElement>, "ref"> & React.RefAttributes<HTMLParagraphElement>>;
export type FieldErrorProps = React.ComponentPropsWithoutRef<typeof BaseField.Error>;
/**
 * A validation message.
 *
 * **`<Field invalid>` shows this, which is a divergence from Base UI and a deliberate one.**
 * `BaseField.Error` renders only when `match` is given: the root's `invalid` prop sets
 * `aria-invalid` and `data-invalid` — so every visual treatment keyed to invalid fires — while the
 * message itself stays absent, because Base UI gates it on the control's own `ValidityState` rather
 * than on the prop. A field that turns red and says nothing was the result, and every consumer using
 * an external validator (Formik, React Hook Form, Zod) hit it and had to learn to pass `match`
 * themselves. That is a trap, not an API: the prop that says "this field is invalid" should show the
 * message that says why.
 *
 * So `match` defaults to the root's `invalid`, and stays overridable:
 *
 * - nothing — follows `<Field invalid>`. The external-validator case, which is most of them.
 * - `match="valueMissing"` and friends — native constraint validation, unchanged.
 * - `match={false}` — explicitly suppress, even on an invalid field.
 *
 * A `Field` that sets no `invalid` is unaffected and still gates on `ValidityState`, so native
 * validation behaves exactly as before. Base UI's own behaviour is pinned in
 * `base-ui-field.characterisation.test.tsx`; this wrapper's divergence is asserted in
 * `field.test.tsx`.
 */
export declare const FieldError: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldErrorProps, "ref"> & React.RefAttributes<HTMLDivElement>, "ref"> & React.RefAttributes<HTMLDivElement>>;
export type FieldGroupProps = React.HTMLAttributes<HTMLDivElement>;
/** A stack of fields, at the vertical rhythm a form wants rather than the one a field wants. */
export declare const FieldGroup: React.ForwardRefExoticComponent<FieldGroupProps & React.RefAttributes<HTMLDivElement>>;
export type FieldSetProps = React.ComponentPropsWithoutRef<typeof BaseFieldset.Root>;
/**
 * A group of related fields with a shared name — the accessible name a radio group usually lacks.
 *
 * `Fieldset.Root` rather than a `<div role="group">`: Base UI associates the legend, which is what
 * makes the group announced rather than merely visually boxed.
 */
export declare const FieldSet: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldsetRootProps, "ref"> & React.RefAttributes<HTMLElement>, "ref"> & React.RefAttributes<HTMLFieldSetElement>>;
export type FieldLegendProps = React.ComponentPropsWithoutRef<typeof BaseFieldset.Legend>;
export declare const FieldLegend: React.ForwardRefExoticComponent<Omit<Omit<import("@base-ui/react").FieldsetLegendProps, "ref"> & React.RefAttributes<HTMLDivElement>, "ref"> & React.RefAttributes<HTMLLegendElement>>;
export type FieldContentProps = React.HTMLAttributes<HTMLDivElement>;
/** A row that puts a control beside its label — a switch or a checkbox, rather than above it. */
export declare const FieldContent: React.ForwardRefExoticComponent<FieldContentProps & React.RefAttributes<HTMLDivElement>>;
export type FieldTitleProps = React.HTMLAttributes<HTMLDivElement>;
/** A heading for a `FieldSet` that is not its legend — a section title inside a long form. */
export declare const FieldTitle: React.ForwardRefExoticComponent<FieldTitleProps & React.RefAttributes<HTMLDivElement>>;
export type FieldSeparatorProps = React.HTMLAttributes<HTMLDivElement>;
/** A rule between groups of fields. Decoration, so it is hidden from assistive technology. */
export declare const FieldSeparator: React.ForwardRefExoticComponent<FieldSeparatorProps & React.RefAttributes<HTMLDivElement>>;
//# sourceMappingURL=field.d.ts.map