@object-ui/fields 17.5.0 → 17.7.0

package/dist/widgets/ObjectRefField.d.ts

@@ -1,4 +1,4 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 export declare function ObjectRefField({ value, onChange, readonly, className, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
 export default ObjectRefField;

package/dist/widgets/OptionsEmptyState.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { HostGroupProps } from './toHostGroupProps';
+import { HostControlProps, HostGroupProps } from './toHostGroupProps.js';
 /**
  * The "this option list cannot be filled" state shared by every fixed-option
  * widget (`SelectField` single, `MultiSelectField`, `RadioField`,
@@ -46,14 +46,44 @@ export interface OptionsEmptyStateProps {
      * The host label's IDREF plumbing, when this box is the whole rendered surface
      * of a group-labelled field (objectui#3990) — a `checkboxes` / `radio` /
      * `multiselect` whose option list came back empty renders NOTHING but this
-     * box, so the visible label named zero elements until it landed here.
+     * box, so the visible label named zero elements until it landed here. Its
+     * help text described zero elements for the same reason, which is why the
+     * callers ask `toHostGroupProps` for the `'instead-of-the-inputs'` surface:
+     * there is no option control in this state to announce the description on
+     * (objectui#4005).
      *
-     * A closed three-key type rather than an open props tail: only `id`,
-     * `aria-labelledby` and the `role` that makes them meaningful may reach this
-     * element, and reopening a spread is what objectui#3291 exists to prevent.
-     * Absent for the single `SelectField` — it is not group-labelled, its label
-     * still uses a plain `for`, and it must keep emitting no such attributes.
+     * A closed type rather than an open props tail: only `id`, `aria-labelledby`,
+     * `aria-describedby` and the `role` that makes them meaningful may reach this
+     * element, and reopening a spread is what objectui#3291 exists to prevent —
+     * `aria-invalid` / `aria-required` are control-channel state and stay off this
+     * surface. Absent for the single `SelectField`, which is not group-labelled
+     * and fills {@link OptionsEmptyStateProps.hostControlProps} instead.
      */
     hostGroupProps?: HostGroupProps;
+    /**
+     * The host label's PLAIN-`for` plumbing, for the one caller that is NOT
+     * group-labelled — the single `SelectField` (objectui#8803).
+     *
+     * Supplying this switches the rendered element from a `div` to an `<output>`,
+     * and that is the entire repair. `select` declares `labelling: 'control'`,
+     * which the registry defines as "the component's outermost rendered element
+     * is a LABELABLE HTML element" — true of the Radix
+     * `button[role="combobox"]` it renders with options, and FALSE of the `div`
+     * this box used to be. So the host's `for` pointed at an id no element
+     * carried, and `HTMLLabelElement.control` was null. Landing the id on the
+     * `div` instead was measured and rejected: `for` may only reference a
+     * labelable element, so it stayed null and the label stayed unusable.
+     *
+     * `<output>` is labelable, and its implicit `status` role claims no
+     * interactivity — it is the result of a computation, which is what this box
+     * reports. Declaring `select` as `'group'` was the alternative and it
+     * measurably moved the LIVE path: a select WITH options lost the working
+     * `<label for>` to its combobox (objectui#3306).
+     *
+     * Mutually exclusive with `hostGroupProps` — one host, one naming channel
+     * (objectui#3978). A caller that supplies neither renders the box with no
+     * host plumbing at all, which is what standalone rendering has always done.
+     */
+    hostControlProps?: HostControlProps;
 }
-export declare function OptionsEmptyState({ emptyHint, gated, dependsOnFields, testId, className, hostGroupProps, }: OptionsEmptyStateProps): React.JSX.Element;
+export declare function OptionsEmptyState({ emptyHint, gated, dependsOnFields, testId, className, hostGroupProps, hostControlProps, }: OptionsEmptyStateProps): React.JSX.Element;

package/dist/widgets/PasswordField.d.ts

@@ -1,7 +1,21 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * PasswordField - Secure password input with visibility toggle
  * Includes show/hide toggle button and masks value in readonly mode
+ *
+ * Readonly draws the mask for a credential that is SET, and the shared
+ * `EmptyValue` affordance for one that is NOT (objectui#10639). The platform's
+ * read contract is presence-preserving: `@objectstack/spec`'s `SECRET_MASK`
+ * docblock says an unset credential "reads back `null` instead, never this
+ * mask", which is what lets a reader tell "configured" from "not configured".
+ *
+ * "Empty" is the password CELL's predicate (`MaskedCellRenderer` in this
+ * package's barrel, objectui#8678), called on the same two helpers, so `{}`
+ * and a whitespace-only string stay values and keep the mask. The helpers are
+ * imported from their own modules, never from the barrel, which lazy-loads
+ * this widget. ⛔ The value is never printed, and a set value keeps exactly
+ * the mask it drew before. `__tests__/PasswordField.readonlyEmpty-10639`
+ * pins the widget's "empty" to the cell's.
  */
 export declare function PasswordField({ value, onChange, field, readonly, className, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/PeoplePicker.d.ts

@@ -27,12 +27,27 @@ export interface PeoplePickerProps {
     dataSource: DataSource;
     /** Object to query — `sys_user` for user fields. */
     objectName: string;
+    /**
+     * The person's name field (default `name`), read first of the name ladder
+     * (then `name`, `username`, `label`). Once the permission policy has loaded,
+     * a rung the user may not read on `objectName` is skipped.
+     */
     displayField?: string;
     idField?: string;
-    /** Dotted field paths for the row subtitle, e.g. `['primary_business_unit_id.name','email']`. */
+    /**
+     * Dotted field paths for the row subtitle, e.g. `['primary_business_unit_id.name','email']`.
+     * Once the permission policy has loaded, a path whose field on `objectName`
+     * the user may not read is not drawn.
+     */
     subtitleFields?: string[];
+    /** Avatar image field; not drawn once the loaded policy denies it on `objectName`. */
     avatarField?: string;
-    /** Related entities to expand (e.g. `['primary_business_unit_id']` for the department name). */
+    /**
+     * Related entities to expand (e.g. `['primary_business_unit_id']` for the
+     * department name). Once the permission policy has loaded, a relation the
+     * user may not read on `objectName` is left out, as it is from the list
+     * derived from `subtitleFields` when this is not passed.
+     */
     expand?: string[];
     /** Narrow the server searchable set (ADR-0061). */
     searchFields?: string[];

package/dist/widgets/PercentField.d.ts

@@ -1,7 +1,8 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
- * PercentField - Percentage input with configurable decimal precision
+ * PercentField - Percentage input whose decimal places follow the field's
+ * `scale` as the protocol resolves it (see the read below)
  * Stores values as decimals (0-1) and displays as percentages (0-100%)
  * Includes a slider for interactive control.
  */

package/dist/widgets/PersonRow.d.ts

@@ -10,8 +10,19 @@ import { default as React } from 'react';
 export interface PersonRowProps {
     record: any;
     displayField?: string;
+    /**
+     * The fields the name is read from, in order; defaults to the ladder of
+     * `displayField` (`getPersonNameFields`). PeoplePicker passes the fields of
+     * that ladder the loaded policy lets the viewer read (objectui#10535).
+     */
+    nameFields?: string[];
     subtitleFields?: string[];
-    avatarField?: string;
+    /**
+     * Avatar image field (default `image`). `null` draws no image, only the
+     * initials: what PeoplePicker passes when field-level security withholds the
+     * field (objectui#10433).
+     */
+    avatarField?: string | null;
     selected?: boolean;
     /** Keyboard cursor is on this row — highlight + scroll into view. */
     active?: boolean;
@@ -20,4 +31,4 @@ export interface PersonRowProps {
     onSelect?: (record: any) => void;
     className?: string;
 }
-export declare function PersonRow({ record, displayField, subtitleFields, avatarField, selected, active, highlightQuery, onSelect, className, }: PersonRowProps): React.JSX.Element;
+export declare function PersonRow({ record, displayField, nameFields, subtitleFields, avatarField, selected, active, highlightQuery, onSelect, className, }: PersonRowProps): React.JSX.Element;

package/dist/widgets/PhoneField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * PhoneField - Telephone number input with tel link in readonly mode
  * Renders as a clickable tel link when readonly, standard phone input otherwise

package/dist/widgets/QRCodeField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * QR Code field widget - generates QR codes from text
  * Uses a simple SVG-based QR code generator

package/dist/widgets/RadioField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * RadioField - choose exactly one value from a fixed option set, rendered as a
  * radio group. The stored value is the selected option value (string). Used for

package/dist/widgets/RatingField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Rating field widget - provides a star rating input
  * Supports numeric values from 0 to max (default 5)

package/dist/widgets/RecipientPickerField.d.ts

@@ -1,4 +1,47 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
+/** A user-valued column offered by the `field` recipient mode. */
+interface UserFieldDef {
+    /** The machine name — this is what gets stored in `recipient_id`. */
+    name: string;
+    label: string;
+}
+/**
+ * Does this declared field hold USERS?
+ *
+ * ⭐ This predicate is the picker's half of a two-sided agreement with the
+ * sharing evaluator, which asks the same question of the same two spellings:
+ * the `user` type (whose target is fixed to `sys_user` by the type itself —
+ * `Field.user()` takes no target), and a `lookup` / `master_detail` whose
+ * `reference` is `sys_user`.
+ *
+ * ⛔ The two must not drift apart. The evaluator treats a column that is not
+ * user-typed as "grants nobody" and warns once per rule, so a picker that
+ * OFFERED a wider set would let an admin save a rule that looks configured and
+ * authorises nobody — worse than the hand-typed name this mode replaces,
+ * because it has a credible appearance.
+ *
+ * `reference` is the only spelling the protocol declares (objectui#6837):
+ * `FieldSchema` refuses `reference_to` by name, and the evaluator reads
+ * `reference` as well.
+ *
+ * @internal exported for tests
+ */
+export declare function fieldHoldsUsers(def: unknown): boolean;
+/**
+ * The user-valued columns of an object schema, in declaration order.
+ *
+ * Accepts both shapes an object schema spells `fields` in — a name-keyed map
+ * and an array of definitions carrying their own `name`.
+ *
+ * ⛔ `hidden` is deliberately NOT filtered here, unlike the filter builder's
+ * own field derivation: the evaluator honours a hidden user column exactly
+ * like a visible one, and withholding it would break the agreement above in
+ * the other direction — an authorable, working configuration the picker
+ * refuses to offer.
+ *
+ * @internal exported for tests
+ */
+export declare function deriveUserFields(schema: any): UserFieldDef[];
 export declare function RecipientPickerField({ value, onChange, readonly, className, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
 export default RecipientPickerField;

package/dist/widgets/RecordPickerDialog.d.ts

@@ -1,13 +1,11 @@
 import { default as React } from 'react';
 import { DataSource, LookupColumnDef, LookupFilterDef } from '@object-ui/types';
+import { LookupCellRendererResolver } from './lookupColumnDisplay.js';
 /**
  * Cell renderer function signature — matches getCellRenderer from @object-ui/fields.
  * Accepts a field type and returns a React component that renders a formatted cell.
  */
-export type CellRendererResolver = (fieldType: string) => React.FC<{
-    value: any;
-    field: any;
-}>;
+export type CellRendererResolver = LookupCellRendererResolver;
 /**
  * Filter column definition used by the inline filter bar.
  * A subset of LookupColumnDef enriched with filter-specific metadata.
@@ -43,7 +41,12 @@ export interface RecordPickerFilterBarProps {
  * Allows plugging in ObjectGrid or any compatible table component.
  */
 export interface RecordPickerGridSlotProps {
-    /** Resolved column definitions */
+    /**
+     * Resolved column definitions, less the ones field-level security denies
+     * once the permission policy has loaded, the display column included — the
+     * columns the built-in table draws (objectui#10373). When none survives,
+     * this is the id column alone.
+     */
     columns: LookupColumnDef[];
     /** Current page of records */
     records: any[];
@@ -95,16 +98,30 @@ export interface RecordPickerDialogProps {
     objectName: string;
     /** Columns to display. Defaults to [displayField, descriptionField]. */
     columns?: Array<string | LookupColumnDef>;
-    /** Primary display field (default: 'name') */
+    /**
+     * The display field as the lookup DECLARES it. The display column is keyed on
+     * it, or on `'name'` when it is omitted. With `objectSchema` given, a declared
+     * value is also the first rung of the column's title (the resolver's
+     * `titleField`); the `'name'` default never is, because it is a guess and a
+     * guess never outranks the referenced object's own declarations. So pass
+     * `undefined` when the field declares none, never a pre-filled `'name'`.
+     */
     displayField?: string;
     /**
-     * Optional `titleFormat` template (e.g. `"{full_name}"` or
-     * `"{case_number} - {subject}"`). When set and the displayField column is
-     * auto-inferred, the column renders via the template instead of reading
-     * a possibly-missing field. Mirrors how DetailView/ObjectCalendar resolve
-     * record titles.
+     * The referenced object's schema (objectui#10486). When given, the display
+     * column renders each record's title through `@object-ui/core`'s
+     * `getRecordDisplayName`, the call LookupField's dropdown option label and
+     * the read cell make: the declared `displayField`, then the object's
+     * `nameField`, then its deprecated `titleFormat` template, then type-aware
+     * derivation (ADR-0079). The title reads the row with its relations
+     * collapsed to ids and the fields the loaded policy denies removed, exactly
+     * as the dropdown's option label does.
+     *
+     * Replaces the retired `titleFormat` prop: a bare template cut out of the
+     * schema ranked above the `nameField` beside it, so the picker and the
+     * dropdown labelled one record two ways.
      */
-    titleFormat?: string | null;
+    objectSchema?: Record<string, unknown> | null;
     /** Record id field (default: 'id') */
     idField?: string;
     /** Page size (default: 10) */
@@ -121,7 +138,7 @@ export interface RecordPickerDialogProps {
     onSelectRecords?: (records: any[]) => void;
     /**
      * Base filters applied to every query.
-     * Converted from LookupFieldMetadata.lookup_filters.
+     * Converted from LookupFieldMetadata.lookupFilters.
      * Restricts which records are selectable (e.g. only active records).
      */
     lookupFilters?: LookupFilterDef[];
@@ -147,7 +164,7 @@ export interface RecordPickerDialogProps {
      *   (`before`, `after`, `is_empty`, `is_not_empty`) the record form has no
      *   `$op` for. No second operator vocabulary is introduced here: two already
      *   exist (the spec's `AST_OPERATOR_MAP`, data-objectstack's
-     *   `FILTER_OPERATOR_ALIASES`) and #3948 is what a third costs.
+     *   `FILTER_OPERATOR_ALIASES`) and objectstack-ai/objectstack#3948 is what a third costs.
      *
      * The discriminator is exact rather than heuristic — every AST node is an
      * ARRAY and a rule is a plain OBJECT, the same predicate `toFilterNode` uses.
@@ -170,7 +187,7 @@ export interface RecordPickerDialogProps {
      * The referenced object's schema `fields` map (field name → field
      * definition). When provided, cell renderers receive the FULL field
      * metadata — `options`, `currency`, `scale`, `precision`, `format`,
-     * `reference_to`, … — exactly like the list view enriches its columns from
+     * `reference`, … — exactly like the list view enriches its columns from
      * the object schema. Without it a `select` column falls back to
      * title-casing the raw stored value instead of resolving the option label
      * (#3333: `manufacturing` rendered as "Manufacturing" instead of the
@@ -227,4 +244,4 @@ export interface RecordPickerDialogProps {
  * states, and single/multi-select.  Responsive: mobile-friendly width
  * via Tailwind breakpoints.
  */
-export declare function RecordPickerDialog({ open, onOpenChange, title, multiple, dataSource, objectName, columns: columnsProp, displayField, titleFormat, idField, pageSize, value, onSelect, onSelectRecords, lookupFilters, baseFilter, cellRenderer, fieldsMeta, filterColumns, renderFilterBar, renderGrid, }: RecordPickerDialogProps): React.JSX.Element;
+export declare function RecordPickerDialog({ open, onOpenChange, title, multiple, dataSource, objectName, columns: columnsProp, displayField: declaredDisplayField, objectSchema, idField, pageSize, value, onSelect, onSelectRecords, lookupFilters, baseFilter, cellRenderer, fieldsMeta, filterColumns, renderFilterBar, renderGrid, }: RecordPickerDialogProps): React.JSX.Element;

package/dist/widgets/RichTextField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Rich text field with markdown/HTML support
  * For now, this is a simple textarea. A full implementation would use
@@ -22,5 +22,41 @@ import { FieldWidgetComponentProps } from './types';
  * tolerant fallback in one of them. The affordance and dialog themselves come
  * from the shared `FullscreenFieldEditor`, so one form-level setting keeps
  * producing one behaviour across both widgets.
+ *
+ * ## Readonly display (`4bb940b6e`)
+ *
+ * The readonly early return used to render `{value}` as a React TEXT CHILD,
+ * so a readonly field of any of the three types showed the user the markup
+ * SOURCE of their own content — a `markdown` field's asterisks and hashes, a
+ * `richtext` field's tags. The `prose` classes on that wrapper were the tell:
+ * they exist to style RENDERED rich content and there was none to style. Every
+ * other read surface — grid, kanban card, gallery, related list, dashboard
+ * record panel, record detail read mode — dispatches through `getCellRenderer`
+ * and renders the same stored bytes FORMATTED, so one field disagreed with
+ * itself depending on which surface it was read on, and this branch was the
+ * one disagreeing with the platform.
+ *
+ * It now renders through {@link richTextCellRenderer} — literally the same
+ * components `getCellRenderer` resolves, one table shared by both (see
+ * `./richTextDisplay.tsx`), so the html/richtext path carries that renderer's
+ * `sanitizeHtml` trust boundary rather than a second hand-rolled escape, and a
+ * future change to either pipeline moves both surfaces at once.
+ *
+ * ## Host plumbing (objectui#4810)
+ *
+ * The editable branch had no `toDomProps` at all, so everything
+ * `<FormControl>`'s Radix `Slot` hands down — the field's `id`, the
+ * `aria-describedby` naming its `<FormDescription>` and `<FormMessage>` —
+ * arrived as props and landed on no element. Measured on a real form: the
+ * visible label's `for` pointed at an id nothing carried (`for=DANGLING`) and
+ * the rendered description had zero consumers, for all three registry keys
+ * (`markdown` / `html` / `richtext`) since they are this one widget.
+ *
+ * The fix is objectui#3318's standing recipe — `toDomProps(props)` spread onto
+ * the REAL focusable control, which here is the `<Textarea>` inside
+ * `RichTextEditorSurface`, never the wrapper `<div>`s (a non-focusable wrapper
+ * carrying the id would satisfy `document.getElementById` and still leave the
+ * label inert). Only the inline surface receives it; see `domProps` there for
+ * why the dialog's copy must not.
  */
 export declare function RichTextField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/SelectField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * SelectField - dropdown selection widget.
  *

package/dist/widgets/SelectionTray.d.ts

@@ -12,7 +12,18 @@ export interface SelectionTrayProps {
     /** Remove a selected record by its id. */
     onRemove: (id: any) => void;
     displayField?: string;
-    avatarField?: string;
+    /**
+     * The fields each chip's name is read from, in order; defaults to the ladder
+     * of `displayField` (`getPersonNameFields`). PeoplePicker passes the fields
+     * of that ladder the loaded policy lets the viewer read (objectui#10535).
+     */
+    nameFields?: string[];
+    /**
+     * Avatar image field (default `image`). `null` draws no image, only the
+     * initials: what PeoplePicker passes when field-level security withholds the
+     * field (objectui#10433).
+     */
+    avatarField?: string | null;
     idField?: string;
     /** Header label, e.g. "Selected (3)" — omit to hide the header. */
     label?: string;
@@ -24,4 +35,4 @@ export interface SelectionTrayProps {
     emptyText?: string;
     className?: string;
 }
-export declare function SelectionTray({ records, onRemove, displayField, avatarField, idField, label, onClear, clearLabel, emptyText, className, }: SelectionTrayProps): React.JSX.Element;
+export declare function SelectionTray({ records, onRemove, displayField, nameFields, avatarField, idField, label, onClear, clearLabel, emptyText, className, }: SelectionTrayProps): React.JSX.Element;

package/dist/widgets/SignatureField.d.ts

@@ -1,7 +1,37 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Signature field widget - provides a signature pad for capturing signatures
  * Outputs signature as a base64 PNG image
+ *
+ * ## Naming, and the half that is deliberately absent (objectui#3318)
+ *
+ * This widget forwarded nothing a host handed it — every branch below wrote its
+ * attributes by hand — so its visible label pointed `for` at an id no element
+ * in the row carried, and the rendered help text had zero consumers. Measured
+ * on `origin/main`, a real form, this field required and freshly failed:
+ *
+ * ```
+ * signature  labelFor=…-form-item -> DANGLING  descConsumers=0  ids=[]
+ * ```
+ *
+ * The name and the description arrive here, on the container, through
+ * {@link toHostGroupProps} — the objectui#3961 route for a widget whose surface
+ * no `<label for>` can reach (`<canvas>` is not a labelable element), and which
+ * therefore declares `labelling: 'group'` in `FIELD_WIDGET_LABELLING`.
+ * `'instead-of-the-inputs'` because this field renders no input of its own for
+ * the description to land on: the Clear button is auxiliary — it acts on the
+ * value, it is not the value's control — the same reading that put
+ * `geolocation`'s focusable "View on map" link on that side of the split.
+ *
+ * `aria-invalid` and `aria-required` are NOT here, and their absence is a
+ * verdict rather than an omission. The drawing surface has no keyboard path at
+ * all (measured: this row offers zero focusable elements while empty — the only
+ * candidate, Clear, is `disabled` until something has been drawn), so there is
+ * no element assistive technology would read a control state from. Marking the
+ * container instead would announce a state with no control behind it — the
+ * non-focusable-wrapper move objectui#3291 and #3318 both draw the line
+ * against. The type is recorded in that sweep's NOT_APPLICABLE ledger with a
+ * guard that turns red the day a real control appears here.
  */
-export declare function SignatureField({ value, onChange, readonly }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function SignatureField({ value, onChange, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/SliderField.d.ts

@@ -1,7 +1,42 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Slider field widget - provides a range slider input
  * Supports numeric values with configurable min, max, and step
+ *
+ * ## Where the host's facts go, and why (objectui#3318)
+ *
+ * This widget used to read exactly two keys off its props (`disabled`,
+ * `className`) and forward nothing else, so everything `<FormControl>`'s Slot
+ * delivered was dropped on the floor. Measured on `origin/main`, a real form
+ * with a required slider that had just failed validation:
+ *
+ * ```
+ * ariaInvalidTrue=[]   labelFor=…-form-item -> DANGLING
+ * descConsumers=0      ids=[]   <- no element of the row carried an id at all
+ * ```
+ *
+ * Three channels, one cause. The DOM pass-through now goes to the THUMB — the
+ * `span[role="slider"]` a keyboard user lands on, which is where ARIA state
+ * belongs — through the `thumbProps` the primitive grew for this
+ * (`lib/slider-thumb.ts`; the shadcn `ui/slider.tsx` renders its thumb
+ * internally and exports only `Slider`, so it cannot be addressed from here
+ * the way objectui#3306 addressed `SelectTrigger`).
+ *
+ * The split of which keys stay on Root is `SelectField`'s, key for key:
+ *
+ * - `name`: Root owns the hidden input that takes part in form submission; on
+ *   a `span` it is not even DOM-legal, and is exactly the leak objectui#3291
+ *   sweeps for.
+ * - `disabled`: Root is the single authority (it disables the thumb and the
+ *   hidden input together); forwarding the raw prop to the thumb as well would
+ *   give the state a second, OR-merged author.
+ *
+ * The visible label reaches the thumb by IDREF, not by `for`: a
+ * `span[role="slider"]` is not one of HTML's labelable elements, so this widget
+ * is declared `labelling: 'group'` for the same reason `file` is — see
+ * `FIELD_WIDGET_LABELLING` in `../index` and objectui#3961. No extra
+ * `role="group"` wrapper: there is one control here, and `slider` is a role
+ * that carries a name perfectly well on its own.
  */
-export declare function SliderField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;
+export declare function SliderField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;

package/dist/widgets/SummaryField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * SummaryField - Read-only aggregation field
  * Values are aggregated from related records and cannot be edited

package/dist/widgets/TagsField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * TagsField - free-form list of string tags. Type a value and press Enter (or
  * comma) to add it; click a tag's × to remove it. The stored value is a

package/dist/widgets/TextAreaField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * TextAreaField - Multi-line text input widget
  * Supports configurable row count and preserves whitespace in readonly mode.
@@ -35,7 +35,11 @@ import { FieldWidgetComponentProps } from './types';
  * ## The character counter (objectui#3408, shared across surfaces in #3417)
  *
  * Both editing surfaces below — the inline `<Textarea>` and the fullscreen
- * dialog's — render the SAME `CharacterCount`, which owns the three-node
+ * dialog's — render the SAME `CharacterCount`. It lives in
+ * `@object-ui/components` since objectui#3439, hoisted there so the form
+ * renderer's built-in `textarea` branch renders that very component too rather
+ * than growing a third copy; this widget's use of it is unchanged. It owns the
+ * three-node
  * GOV.UK shape (decorative digits / accessible description / gated status
  * region) and the debounce and threshold behind it. Until #3417 the fullscreen
  * footer had its own hand-written copy that was digits and nothing else, which

package/dist/widgets/TextField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * TextField - Standard single-line or multi-line text input
  * Automatically renders as a textarea when rows are configured in field metadata
  */
-export declare function TextField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function TextField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/TimeField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * TimeField - Time picker input widget
  * Uses native time input for hour and minute selection
  */
-export declare function TimeField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function TimeField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/UrlField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * UrlField - URL input with clickable link in readonly mode
  * Validates URLs to only render http/https links for security

package/dist/widgets/UserField.d.ts

@@ -1,3 +1,3 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 export declare function UserField(props: FieldWidgetComponentProps<any>): React.JSX.Element;

package/dist/widgets/VectorField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * VectorField - Vector/embedding data display
  * Shows vector embeddings in a read-only format

package/dist/widgets/_cell-renderer-bridge.d.ts

@@ -1,3 +1,3 @@
-import { CellRendererResolver } from './RecordPickerDialog';
+import { CellRendererResolver } from './RecordPickerDialog.js';
 export declare function setCellRendererResolver(resolver: CellRendererResolver): void;
 export declare function getCellRendererResolver(): CellRendererResolver | undefined;