No matches.
component
Validation error(s). A non-empty value flips the control's `tone` to `danger`, renders the message(s) as a list inside an `alert` live region, and sets `aria-invalid` / `aria-errormessage` on the control.
Optional-hint text shown after the label when the field is NOT required (e.g. "(optional)"). Ignored when `required` is true.
Explicit tone override for the control. When unset, the field derives `danger` from the presence of an `error`, and otherwise leaves the control's own resting default untouched (e.g. Input `neutral`, Checkbox `primary`).
Whether a description element is rendered — gates the input's `aria-describedby` (an ungated reference dangled on description-less fields). Frameworks set this from their description prop/slot.
Whether a visible label is rendered. When true (and an `id` is set), the connect seeds a label id and associates the control via `aria-labelledby`. Frameworks set this when label content is provided.
Whether a label tooltip trigger is rendered, so the connect emits its styling bag. Frameworks set this when a tooltip is provided.
Stable id linking the `<label for>` to the control and seeding the `aria-describedby` / `aria-errormessage` ids. Frameworks generate one when the consumer doesn't pass it. When absent, the label/describedby wiring is omitted (the field still renders).
Render-prop for the control — receives the props bag to spread onto it.
Astro / vanilla: serialize the props into `data-field-config` so the client runtime hydrates this instance and `getPindoba(el, "field")` can `update()` it. Frameworks with their own reactivity don't need it.