@object-ui/fields 17.3.0 → 17.6.0

package/dist/widgets/richTextDisplay.d.ts

@@ -0,0 +1,80 @@
+import { default as React } from 'react';
+import { CellRendererProps } from '../index.js';
+/**
+ * Renders `markdown` values as formatted GFM markdown (lazy-loaded, sanitized)
+ * instead of the raw markup string.
+ *
+ * Markdown ONLY. `MarkdownContent` runs react-markdown with no `rehype-raw`, so
+ * raw HTML in the string is not parsed and never reaches the DOM — that is this
+ * renderer's trust boundary, not an oversight, and it must stay that way
+ * (objectui#5452). `richtext` used to be routed here too and rendered as a
+ * COMPLETELY EMPTY cell, because a richtext value is entirely HTML and this
+ * pipeline drops all of it; see {@link HtmlCellRenderer}, which is where that
+ * type belongs. Loosening this pipeline to pass raw HTML through would have
+ * "fixed" one type by moving every `markdown` cell's trust boundary.
+ */
+export declare function MarkdownCellRenderer({ value }: CellRendererProps): React.ReactElement;
+/**
+ * Renders an `html` value as sanitized, formatted HTML instead of raw markup.
+ *
+ * Also the renderer for `richtext` (objectui#5452). Both types store an HTML
+ * string: the spec's `Field.richtext` is documented as "Formatted content with
+ * HTML/WYSIWYG", the showcase seed's own specimen is
+ * `<p>Rich <strong>text</strong></p>`, and this repo's designer bridge already
+ * maps `richtext` onto its `html` type. {@link sanitizeHtml} above removes
+ * script/style/iframe/object/embed blocks, inline event handlers and
+ * `javascript:` URLs, and touches nothing a rich-text editor legitimately
+ * emits — headings, paragraphs, emphasis, lists, links, quotes all survive, so
+ * routing `richtext` here restores the content rather than trading a blank cell
+ * for a mangled one.
+ */
+export declare function HtmlCellRenderer({ value }: CellRendererProps): React.ReactElement;
+/**
+ * Field type → display pipeline, for the three types `RichTextField` serves.
+ *
+ * THE table, singular. `getCellRenderer`'s standard map spreads it (so the
+ * grid, kanban, gallery, related list, dashboard panel and detail read mode
+ * resolve through these entries) and `RichTextField`'s readonly branch indexes
+ * it (so a readonly form field renders through the very same component). A
+ * change here moves every read surface at once; there is no second copy left
+ * to forget.
+ *
+ * `richtext` reads through the HTML renderer — NOT the markdown one, which
+ * drops raw HTML and therefore rendered every populated richtext value as a
+ * blank cell (objectui#5452).
+ */
+export declare const RICH_TEXT_CELL_RENDERERS: {
+    readonly markdown: typeof MarkdownCellRenderer;
+    readonly html: typeof HtmlCellRenderer;
+    readonly richtext: typeof HtmlCellRenderer;
+};
+/** The rich-content field types, i.e. the keys of {@link RICH_TEXT_CELL_RENDERERS}. */
+export type RichTextFieldType = keyof typeof RICH_TEXT_CELL_RENDERERS;
+/**
+ * The SYNTAX a rich-content type stores, derived from the renderer that type
+ * resolves to rather than declared a second time.
+ *
+ * This is what `RichTextField`'s editor header names ("Format: markdown"), and
+ * deriving it from {@link RICH_TEXT_CELL_RENDERERS} is the point: the header
+ * used to be computed as `field.format || 'markdown'`, and since `format` is
+ * declared on no rich-content field type (only on `date`/`datetime`/`time`/
+ * `phone`/`auto_number`), it read `undefined` for every real field and labelled
+ * an `html` field "Format: markdown" — a label pointing at a pipeline the value
+ * does not go through. Derived, the label cannot disagree with the renderer.
+ *
+ * `undefined` for a type with no pipeline, rather than a guessed default: the
+ * caller has to say what it does with "not a rich-content type" instead of
+ * silently getting the markdown answer, which is the bug this replaces.
+ */
+export declare function richTextSyntax(fieldType: string): 'markdown' | 'html' | undefined;
+/**
+ * The display pipeline a field type reads through, or `undefined` when the
+ * type is not one of the three rich-content types.
+ *
+ * The lookup is a function rather than a raw index so the "not a rich-content
+ * type" answer is in the RETURN TYPE. Indexing {@link RICH_TEXT_CELL_RENDERERS}
+ * directly hands back a non-optional component for any key the caller casts,
+ * so the miss becomes a runtime `undefined` the compiler has been told cannot
+ * happen — and a caller that checks for it reads as dead code.
+ */
+export declare function richTextCellRenderer(fieldType: string): React.FC<CellRendererProps> | undefined;

package/dist/widgets/toDomProps.d.ts

@@ -1,10 +1,4 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
+import { DomProps as CoreDomProps } from '@object-ui/core';
 /**
  * The RUNTIME EXECUTOR of the "DOM pass-through" section of
  * {@link FieldWidgetComponentProps} (objectui#3291).
@@ -59,13 +53,39 @@
  * open spread. If a field node should be able to author one, DECLARE it on
  * `FieldWidgetComponentProps` first and add it here — do not reopen the spread
  * (AGENTS.md #0.1: fix the contract, never widen the consumer).
+ *
+ * ## Where the mechanism lives now, and why the key list stayed here
+ *
+ * objectui#4425 phase 2 promoted this whitelist to the SDUI widget contract
+ * generally, so the MECHANISM — filter by a declared key list plus the `aria-*`
+ * / `data-*` open families — moved to `@object-ui/core`
+ * (`utils/dom-props.ts`, `pickDomProps`), where every plugin package can reach
+ * it without depending on `@object-ui/fields` (the objectui#4409
+ * dependency-direction method: `plugin-chatbot` declares `@object-ui/core` and
+ * does not declare this package).
+ *
+ * The KEY LIST did not move, because it is not the same list. Measured on
+ * objectui#4431:
+ *
+ *  - `name` and `disabled` are here and NOT in the SDUI set: both are legal
+ *    only on form controls, which is what every widget in this package renders
+ *    and what `FieldWidgetComponentProps` declares. `name` on the `<div>` an
+ *    SDUI container widget renders is a leak — one of the 14 attributes #4431
+ *    closed — and two widgets here already hand-strip it when they spread onto
+ *    something that is not a control (`ObjectRefField`'s trigger,
+ *    `FileField`'s dropzone).
+ *  - `role` is in the SDUI set and NOT here: `SchemaRenderer` resolves it for
+ *    every node from `@objectstack/spec`'s `AriaPropsSchema`, while this
+ *    contract deliberately does not declare it (see "Deliberately NOT
+ *    forwarded" above).
+ *
+ * So: one mechanism, two declarations, each bound by the assertions below to
+ * the contract it executes. Not two judges.
  */
 declare const DOM_PASS_THROUGH_KEYS: readonly ["id", "name", "autoFocus", "tabIndex", "onBlur", "onFocus", "onClick", "className", "disabled"];
 type DomPassThroughKey = (typeof DOM_PASS_THROUGH_KEYS)[number];
 /** The subset of `P` this helper forwards, with each key's declared type. */
-export type DomProps<P> = Pick<P, Extract<keyof P, DomPassThroughKey>> & {
-    [K in Extract<keyof P, `data-${string}` | `aria-${string}`>]: P[K];
-};
+export type DomProps<P> = CoreDomProps<P, DomPassThroughKey>;
 /**
  * Keep only what may legitimately become a DOM attribute, and drop everything
  * else — renderer plumbing, and any extra key an author put on the field

package/dist/widgets/toHostGroupProps.d.ts

@@ -0,0 +1,189 @@
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+/**
+ * The props that make a group-labelled widget's rendered surface the thing its
+ * host label actually NAMES — and, where nothing else can carry it, DESCRIBES
+ * (objectui#3990, objectui#4005).
+ *
+ * ## What it is for
+ *
+ * A widget declared `labelling: 'group'` (objectui#3961) is told by the form
+ * renderer: your label publishes an `id` and drops its `for`, so name yourself
+ * by IDREF. The renderer hands down facts that address the field as a WHOLE:
+ *
+ *  - `id` — the host's control id (`…-form-item`), the id the label's `for`
+ *    used to point at;
+ *  - `aria-labelledby` — the IDREF of that visible label;
+ *  - `aria-describedby` — the IDREF of `<FormDescription>`, the field's visible
+ *    help text. Which surface may consume it is the one thing that is NOT
+ *    uniform, so it is decided per call site — see {@link HostGroupSurface}.
+ *
+ * Every editable branch already consumes them inside its wider `toDomProps`
+ * spread. The branches that returned EARLY did not — a field-level
+ * `readonly: true`, or an option list with zero offered options — so the label
+ * published an id that no element in the document referenced. Measured on
+ * `origin/main`, one field per row, reading the host label against the DOM:
+ *
+ * ```
+ * multiselect  readonly+value   consumers=0  byLabelText=0  namedByRole=[]
+ * multiselect  readonly+empty   consumers=0  byLabelText=0  namedByRole=[]
+ * multiselect  zeroOptions      consumers=0  byLabelText=0  namedByRole=[]
+ * multiselect  editable         consumers=1  byLabelText=1  namedByRole=[group:1]
+ * ```
+ *
+ * All seven group-labelled types measured the same, in every readonly state.
+ * This is quieter than the dangling `for` #3961 replaced: a `for` that resolves
+ * to nothing can at least be swept for, while "a label published an id and
+ * nobody consumed it" looks like healthy markup.
+ *
+ * ## The description was the other half of the same defect (objectui#4005)
+ *
+ * #3990 landed the `id` + `aria-labelledby` pair above and deliberately stopped
+ * there. The reasoning it recorded — a readonly display has no focusable
+ * control, and `aria-describedby` is announced when focus lands on something
+ * focusable — was the right call for the surface as it stood THEN: before this
+ * helper existed, a readonly branch had no role at all, and on a role-less
+ * `div` / `span` an `aria-describedby` is as inert as the `aria-labelledby`
+ * was. That premise expired the moment #3990 gave those surfaces
+ * `role="group"`. A group IS a description carrier under ARIA 1.2: assistive
+ * technology announces a group's name and description on entering it, with no
+ * focusable control required. So the help text stayed measurably unreachable
+ * for exactly as long as it took to have somewhere to put it. Measured on
+ * `origin/main` at `c25222758`, a real form, one field per row, counting the
+ * elements whose `aria-describedby` names the rendered `<FormDescription>`:
+ *
+ * ```
+ *                                    descEl  consumers  consumerTags
+ * address      editable   desc=YES   SET         1      [input]
+ * address      readonly   desc=YES   SET         0      []
+ * geolocation  editable   desc=YES   SET         1      [input]
+ * geolocation  readonly   desc=YES   SET         0      []
+ * checkboxes   editable   desc=YES   SET         1      [div[group]]
+ * checkboxes   readonly   desc=YES   SET         0      []
+ * radio        editable   desc=YES   SET         1      [div[radiogroup]]
+ * radio        readonly   desc=YES   SET         0      []
+ * rating       editable   desc=YES   SET         1      [div[group]]
+ * rating       readonly   desc=YES   SET         0      []
+ * file         editable   desc=YES   SET         1      [div[button]]
+ * file         readonly   desc=YES   SET         0      []
+ * multiselect  editable   desc=YES   SET         1      [div[group]]
+ * multiselect  readonly   desc=YES   SET         0      []
+ * ```
+ *
+ * All seven render the `<FormDescription>` in the readonly state — none is
+ * exempt for want of one — and all seven left it referenced by nothing.
+ *
+ * ## What still does NOT come along, and why that is a boundary and not an oversight
+ *
+ * `aria-invalid` and `aria-required` are CONTROL-channel state: they report
+ * what a user's own editing may do wrong, to the element they would edit. A
+ * readonly display cannot be edited and cannot be made invalid by the person
+ * reading it, so putting either on it announces a state that has no action
+ * behind it. Spreading the whole `toDomProps` result would drag both back —
+ * along with `disabled` / `tabIndex` / the focus handlers, which only mean
+ * something on an interactive element, and `name`, which is DOM-legal on form
+ * controls only and on a `div` is exactly the leak objectui#3291 sweeps for.
+ * That is what objectui#3291 and objectui#3318 drew the line against, and
+ * adding the description does not move it: the description is what the FIELD
+ * is, the other two are what the CONTROL is doing. The line is pinned from both
+ * sides in `composite-group-label-readonly-e2e.test.tsx` — the description must
+ * be there, `aria-invalid` / `aria-required` must not — so neither a later
+ * "spread it all" nor a later "take it all back out" can pass quietly.
+ *
+ * Spreading the full result would also put the host's `className` on top of the
+ * widget's own, because the widgets whose readonly surface is a placeholder or
+ * a plain container (`EmptyValue`, `FileField`, `AddressField`) keep
+ * `className` inside `props`.
+ *
+ * ## Why `role` travels with the keys
+ *
+ * `aria-labelledby` on a role-less `div` / `span` names NOTHING — `generic`
+ * prohibits an author name — so the pair is inert without a role that supports
+ * naming. `group` is the one that fits a readonly surface: it names a set of
+ * values (chips, checked labels, stars, file names, a formatted address)
+ * without promising the interactivity `textbox` or `radiogroup` would. It is
+ * deliberately NOT the role the same widget answers with while editable:
+ * `RadioField`'s readonly branch renders the chosen label as text with no radios
+ * left in it, and `FileField`'s renders file names with no dropzone button.
+ *
+ * The role is emitted ONLY when a host actually named the field, mirroring
+ * every editable branch's `isLabelledGroup` test: standalone rendering (the
+ * grid's inline cell editor, a bare SDUI node) hands down neither key, so every
+ * value here is `undefined`, React emits no attribute, and that markup stays
+ * byte-identical to what it was.
+ */
+export interface HostGroupProps {
+    /** The host's control id — the id its label would have pointed `for` at. */
+    id?: string;
+    /** IDREF of the host's visible label. */
+    'aria-labelledby'?: string;
+    /**
+     * IDREF of the host's visible help text — present only on a surface that
+     * renders no input of the field's own. See {@link HostGroupSurface}.
+     */
+    'aria-describedby'?: string;
+    /** `'group'` when — and only when — a host named this surface. */
+    role?: 'group';
+}
+/**
+ * WHERE the surface being named sits relative to the field's own inputs. The
+ * name is uniform; the DESCRIPTION is not, so every call site has to say which
+ * of the two shapes it is, and the compiler makes the next widget author say it
+ * too rather than inherit whichever default happened to be there.
+ *
+ *  - `'above-the-inputs'` — a composite's EDITABLE container (`address`,
+ *    `geolocation`): the field's real inputs are inside it and each already
+ *    receives `aria-describedby` in its own `toDomProps` spread, straight from
+ *    `<FormControl>`'s Slot. This surface therefore takes the NAME only.
+ *    objectui#3318 chose that split deliberately and
+ *    `composite-group-label-e2e.test.tsx` pins it: the help text is announced
+ *    when focus reaches the box the user types into, and announcing it a second
+ *    time on the container that merely wraps those boxes is a double channel of
+ *    exactly the kind objectui#3290 removed from the required marker.
+ *
+ *  - `'instead-of-the-inputs'` — every readonly branch, and the zero-option box
+ *    (`OptionsEmptyState`). The field renders no input at all here, so no
+ *    element inside can carry the description and this surface is the only
+ *    candidate there is. It takes the name AND the description.
+ *
+ * Note what the discriminator is NOT about: whether the surface contains
+ * anything focusable. `geolocation`'s readonly row holds a "View on map" link
+ * — focusable, and correctly announced as itself. It is not an input OF THE
+ * FIELD and never receives the field's `aria-describedby`, so that row is still
+ * `'instead-of-the-inputs'`.
+ */
+export type HostGroupSurface = 'above-the-inputs' | 'instead-of-the-inputs';
+/**
+ * Read the whole-field keys out of a widget's leftover props, plus the role
+ * that makes them mean something. See {@link HostGroupProps} and
+ * {@link HostGroupSurface}.
+ *
+ * Routed through {@link toDomProps} rather than reading `props` directly so the
+ * keys keep ONE gate: they reach an element only if the DOM pass-through
+ * whitelist still forwards them, and its compile-time assertions bind that
+ * whitelist to the props contract in both directions.
+ *
+ * `aria-describedby` is forwarded exactly as the host handed it down, with no
+ * check that it resolves — a widget cannot see whether `<FormDescription>`
+ * rendered, and a DOM probe for it would be a layout-effect hack around the
+ * renderer's own knowledge. That is not a new gap: `<FormControl>`'s Slot emits
+ * the IDREF unconditionally, so a field with NO description already hands every
+ * editable control an `aria-describedby` pointing at an element that does not
+ * exist. Measured on `origin/main` at `c25222758`, `desc=NO`: all seven
+ * group-labelled widgets plus the builtin `input` and the single-control
+ * `email` carry exactly one such reference, on the same element that would
+ * carry a resolving one. A readonly surface answering identically is parity
+ * with the editable branch, not a class of its own — and an IDREF that resolves
+ * to nothing is inert for assistive technology, where an unconsumed
+ * description is simply lost.
+ */
+export declare function toHostGroupProps(props: {
+    id?: string;
+    'aria-labelledby'?: string;
+    'aria-describedby'?: string;
+}, surface: HostGroupSurface): HostGroupProps;

package/dist/widgets/types.d.ts

@@ -157,9 +157,14 @@ export type FieldWidgetComponentProps<T = any> = {
     onUploadingChange?: (uploading: boolean) => void;
     /**
      * DataSource for widgets that query records (lookup / user / object-ref /
-     * recipient-picker / grid). Injected by the form renderer for the field
-     * types that need it, and passed directly by inline-edit hosts. Option
-     * widgets destructure it purely to keep it off their DOM spread.
+     * recipient-picker). Injected by the form renderer for the field types that
+     * need it, and passed directly by inline-edit hosts. Option widgets
+     * destructure it purely to keep it off their DOM spread.
+     *
+     * `grid` was listed here with zero consumers (objectui#4814): `GridField.tsx`
+     * never reads `dataSource`, and no data-source table has ever contained the
+     * key, so the claim described a wiring that did not exist. `owner` is absent
+     * for a different reason — the spelling itself is retired (same card).
      *
      * Left structural (`unknown`): `@object-ui/fields` must not depend on a
      * concrete adapter — every consumer narrows it itself.

package/dist/widgets/useRecordQuery.d.ts

@@ -46,8 +46,14 @@ export interface UseRecordQueryOptions {
      * `$filter` — already merged by the caller (base `lookup_filters`, dependent
      * lookup chain, candidate hygiene like `banned != true`, …). Compared by
      * value, so a referentially-new-but-equal object each render will not loop.
+     *
+     * Either the `QueryParams.$filter` record form or a lowered ObjectQL AST node
+     * (an array), since the picker's merge now produces both (#3831). Typed
+     * `unknown` rather than `Record< string, any >` so an array cannot slip
+     * through a type that silently accepts it; emptiness is decided by
+     * {@link hasFilter}, not by `Object.keys`.
      */
-    filter?: Record<string, any>;
+    filter?: unknown;
     /** `$expand` — related entities to include (e.g. `['primary_business_unit_id']`). */
     expand?: string[];
     /** `$searchFields` — narrow the server searchable set (ADR-0061). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/fields",
-  "version": "17.3.0",
+  "version": "17.6.0",
   "description": "Field renderers and registry for Object UI",
   "license": "MIT",
   "type": "module",
@@ -18,37 +18,40 @@
   },
   "files": [
     "dist",
-    "src",
     "README.md",
     "CHANGELOG.md",
     "LICENSE"
   ],
   "dependencies": {
-    "@objectstack/spec": "^17.0.0-rc.2",
+    "@objectstack/spec": "^17.0.0",
     "clsx": "^2.1.1",
-    "lucide-react": "^1.28.0",
+    "lucide-react": "^1.31.0",
     "react-markdown": "^10.1.0",
     "rehype-sanitize": "^6.0.0",
     "remark-gfm": "^4.0.1",
     "tailwind-merge": "^3.6.0",
-    "@object-ui/components": "17.3.0",
-    "@object-ui/core": "17.3.0",
-    "@object-ui/i18n": "17.3.0",
-    "@object-ui/providers": "17.3.0",
-    "@object-ui/react": "17.3.0",
-    "@object-ui/types": "17.3.0"
+    "@object-ui/components": "17.6.0",
+    "@object-ui/core": "17.6.0",
+    "@object-ui/i18n": "17.6.0",
+    "@object-ui/providers": "17.6.0",
+    "@object-ui/react": "17.6.0",
+    "@object-ui/types": "17.6.0"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",
     "react-dom": "^18.0.0 || ^19.0.0"
   },
   "devDependencies": {
+    "@tailwindcss/postcss": "^4.3.3",
     "@types/react": "19.2.18",
     "@types/react-dom": "19.2.4",
     "@vitejs/plugin-react": "^6.0.5",
+    "postcss": "^8.5.26",
+    "tailwindcss": "^4.3.3",
     "typescript": "^6.0.3",
-    "vite": "^8.2.0",
-    "vite-plugin-dts": "^5.0.3"
+    "vite": "^8.2.1",
+    "vite-plugin-dts": "^5.0.3",
+    "@object-ui/test-support": "17.4.0"
   },
   "publishConfig": {
     "access": "public"
@@ -77,9 +80,9 @@
   },
   "homepage": "https://www.objectui.org/docs/fields",
   "scripts": {
-    "build": "tsc && vite build",
+    "build": "tsc && vite build && node scripts/build-css.mjs",
     "clean": "rm -rf dist",
-    "type-check": "tsc --noEmit",
+    "type-check": "tsc --noEmit && tsc -p tsconfig.test.json",
     "test": "vitest run",
     "lint": "eslint ."
   }

package/dist/FieldEditWidget.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/__tests__/resolveFieldCurrency.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/__tests__/spec-symbol-batch7.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/__tests__/widget-props-contract.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/coerce-safe-value.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/complex-widgets.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/datetime-widgets.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/field-type-coverage.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/widgets/CharacterCount.d.ts

@@ -1,56 +0,0 @@
-import { default as React } from 'react';
-export interface CharacterCountProps {
-    /**
-     * Length of the text this surface is counting. The inline surface passes the
-     * committed value's length; the fullscreen dialog passes the DRAFT's, which
-     * is the number that is true of what the user is looking at.
-     */
-    length: number;
-    /**
-     * The declared cap. Callers render this component only when the field
-     * declares one, so it is non-optional here — a counter with no cap to count
-     * against has nothing to say and must not be mounted at all (an unconditional
-     * live region in every long-text field is the objectui#3408 defect back
-     * again).
-     */
-    maxLength: number;
-    /**
-     * The description node's `id`, minted by the host from `useId()`.
-     *
-     * The host MUST also name it in the edited control's `aria-describedby` —
-     * this component renders the sentence, only the host knows which element is
-     * being described, and a description nothing references is a node no screen
-     * reader will ever reach. That association is asserted from the OUTSIDE (the
-     * tests resolve `aria-describedby` and concatenate the referenced nodes' text,
-     * exactly as an assistive technology does) rather than trusted here.
-     *
-     * Two surfaces of one widget therefore need two ids: the dialog's draft and
-     * the inline value diverge the moment the user types in the dialog, so one
-     * shared id would point both controls at whichever sentence rendered last.
-     */
-    descriptionId: string;
-    /**
-     * Render node 3, the threshold-gated debounced `aria-live` status region.
-     *
-     * Required on purpose — see the component doc above. `false` removes the
-     * region from the DOM entirely (not merely empties it), which is the only
-     * form of "no live region" a test can tell apart from "a live region that
-     * happens to be silent right now".
-     */
-    announceNearLimit: boolean;
-    /**
-     * Classes for the visible digits. Required because placement is entirely the
-     * surface's business — inline pins them to the textarea's bottom-right
-     * corner, the dialog lays them out as a footer item — and a default borrowed
-     * from either one would position the other wrongly while looking deliberate.
-     */
-    className: string;
-    /**
-     * `data-testid` for the visible digits, namespaced per surface
-     * (`textarea-character-count`, `textarea-fullscreen-character-count`) so a
-     * test that finds digits can say WHICH surface it found them on. Same
-     * convention, same reason, as `FullscreenFieldEditor`'s `testIdPrefix`.
-     */
-    testId: string;
-}
-export declare function CharacterCount({ length, maxLength, descriptionId, announceNearLimit, className, testId, }: CharacterCountProps): React.JSX.Element;

package/dist/widgets/GridField.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/widgets/ImageLightbox.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/widgets/LookupField.dependsOn.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/widgets/LookupField.gateHintLabel.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/widgets/LookupField.hydration.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/widgets/LookupField.idField.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/widgets/PeoplePicker.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};

package/dist/widgets/PeoplePickerComponents.test.d.ts

@@ -1,8 +0,0 @@
-/**
- * ObjectUI
- * Copyright (c) 2024-present ObjectStack Inc.
- *
- * This source code is licensed under the MIT license found in the
- * LICENSE file in the root directory of this source tree.
- */
-export {};