@object-ui/fields 16.0.0 → 17.1.0

package/README.md

@@ -55,6 +55,23 @@ Supported types out of the box:
 - **Media**: `file`, `image`
 - **System**: `formula`, `summary`, `auto_number`
 
+### Rendering form field widgets outside the form
+
+The full widget surface is exported for consumers that render field widgets
+outside a record form (ADR-0059):
+
+- `FORM_FIELD_TYPES` — the frozen list of every type the form can render.
+- `resolveFormWidgetType(type)` — resolves any field-type spelling to its
+  widget key (spec aliases like `toggle`/`json`/`secret` included; unknown
+  types fall back to `text`, mirroring the form).
+- `getLazyFieldWidget(type)` — the widget wrapped in `React.lazy` (cached per
+  type; render inside `<Suspense>`), sharing the same loaders `registerField`
+  uses so nothing is bundled eagerly.
+
+The app-shell `ActionParamDialog` uses these to render declared action params
+through the exact same widgets as the object form — with a drift test pinning
+param support ⊇ form support.
+
 ### File uploads in line-item grids
 
 `GridField` (the master-detail line-items grid) supports `type: 'file'` columns:
@@ -66,15 +83,36 @@ or photo per row without opening the row form (objectui#2360). Columns accept
 exported as `FileCell`). Auto-derived subform columns map `file`/`image`/
 `avatar` fields to file columns instead of dropping them.
 
+### Multi-value selects
+
+A `select` field declared `multiple: true` selects zero-or-more values (spec
+allows `multiple` on `select`). `SelectField` delegates to the multi-value chip
+picker (the same widget the `multiselect` type uses) and stores a `string[]`.
+Delegating inside `SelectField` — rather than at a type-resolution layer — means
+every surface that renders the `select` widget (the object form, the inline grid
+editor, and the app-shell `ActionParamDialog`) gets multi-select identically,
+with no per-surface drift. Both single- and multi-value selects resolve
+per-option `visibleWhen` cascading and `dependsOn` gating through the same
+[`useCascadingOptions`](./src/widgets/useCascadingOptions.ts) hook, so the
+offered chips narrow (and now-invalid selections are pruned) exactly as the
+single dropdown does.
+
 ### Cascading & role-gated select options
 
-`select` options support a per-option `visibleWhen` CEL predicate (offered only
-when TRUE, evaluated against the live record + `current_user`) and a field-level
-`dependsOn`. Together they drive dependent selects (country → province → city)
-and role-gated options with no bespoke matrix — the same primitives dependent
-lookups use. While a `dependsOn` parent is empty the control is gated; a parent
-change re-filters the list and clears a now-invalid value. Client-side hiding is
-UX only — gate authorization-sensitive values on the server too. See
+`select`, `multiselect`, `radio`, and `checkboxes` options support a per-option
+`visibleWhen` CEL predicate (offered only when TRUE, evaluated against the live
+record + `current_user`) and a field-level `dependsOn`. Together they drive
+dependent selects (country → province → city) and role-gated options with no
+bespoke matrix — the same primitives dependent lookups use. All four widgets
+resolve this through the shared [`useCascadingOptions`](./src/widgets/useCascadingOptions.ts)
+hook, which wraps the pure `resolveCascadingOptions` helper in `@object-ui/core`
+(also used by the form renderer's inline pre-filter, so gating and filtering
+never drift). While a `dependsOn` parent is empty the control is gated; a parent
+change re-filters the list and clears a now-invalid value (scalar `select` /
+`radio` drop the value; multi-value `multiselect` / `checkboxes` prune just the
+offered-out entries).
+Client-side hiding is UX only — gate authorization-sensitive values on the
+server too. See
 [`content/docs/fields/select.mdx`](../../content/docs/fields/select.mdx).
 
 <!-- release-metadata:v3.3.0 -->

package/dist/FieldEditWidget.d.ts

@@ -12,6 +12,13 @@ export declare const INLINE_EXCLUDED_FIELD_TYPES: Set<string>;
 export declare const DISCRETE_EDIT_TYPES: Set<string>;
 /** True when a field type has a dedicated in-place edit widget. */
 export declare function hasFieldEditWidget(type: string | undefined): boolean;
+/**
+ * True when a field type is deliberately NOT inline-editable (alias-aware:
+ * `composite` resolves to the excluded `object`, `video` to `file`, …).
+ * Grid hosts must treat these as read-only cells — falling back to a plain
+ * text editor is exactly the corruption path the exclusion exists to close.
+ */
+export declare function isInlineExcludedFieldType(type: string | undefined): boolean;
 /**
  * Render the dedicated edit widget for a field's type — the SAME control the
  * form uses — as a controlled `{ value, onChange, field }` input. Returns

package/dist/field-type-alias.d.ts

@@ -0,0 +1,16 @@
+/**
+ * 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.
+ */
+/**
+ * Map field type to form component type
+ *
+ * @param fieldType - The ObjectQL field type identifier to convert
+ * (for example: `"text"`, `"number"`, `"date"`, `"lookup"`).
+ * @returns The normalized form field type string used in the form schema
+ * (for example: `"input"`, `"textarea"`, `"date-picker"`, `"select"`).
+ */
+export declare function mapFieldTypeToFormType(fieldType: string): string;