@object-ui/components 13.1.0 → 14.0.0

package/CHANGELOG.md

@@ -1,5 +1,118 @@
 # @object-ui/components
 
+## 14.0.0
+
+### Minor Changes
+
+- 6a74160: Sharing-rule form: pick, don't type. Three new widget-hint field components make
+  the generic object form render pickers where an admin previously had to type
+  machine data (driven by the framework `widget` hints on `sys_sharing_rule`;
+  generalizes the `capability-multiselect` pattern). All degrade to the underlying
+  `type` renderer when a widget is unregistered.
+
+  - **`object-ref`** — choose a registered object by name (searchable `Combobox`),
+    backed by the new `DataSource.getObjects()` (`ObjectStackAdapter` lists code-
+    and DB-defined objects via `/api/v1/meta/object`), falling back to a
+    `sys_metadata` query. Stores the object's `name`.
+  - **`filter-condition`** — a visual criteria builder (`FilterBuilder`) scoped to
+    the fields of the object chosen in a sibling field (via `getObjectSchema`),
+    round-tripping the stored **MongoDB-style** FilterCondition JSON. Criteria the
+    builder can't represent (or invalid JSON) fall back to a raw-JSON editor, with
+    an always-available "Edit as JSON" toggle — nothing is hidden or lost.
+  - **`recipient-picker`** — a record picker whose target object follows a sibling
+    `recipient_type` (`user`→sys_user, `team`→sys_team, `business_unit`/
+    `unit_and_subordinates`→sys_business_unit, `position`→sys_position), storing the
+    value the evaluator matches on (a record id, or the position **name**). Resets
+    the stored id when the type changes.
+
+  Wiring: the three keys join `DATA_SOURCE_FIELD_TYPES` (form.tsx) so the form
+  threads `dataSource` + `dependentValues` to them, and `INLINE_EXCLUDED_FIELD_TYPES`
+  (they're authored in the record form, not a grid cell). `DataSource.getObjects()`
+  is optional on the interface; the ObjectStack adapter implements it.
+
+### Patch Changes
+
+- a44e7b6: Form fields honor their object-schema `widget` render hint on the field-group /
+  section layout path. `ObjectForm` renders objects that declare field groups
+  (e.g. `sys_sharing_rule`) via an auto-derived section layout that passed each
+  field's metadata through without hoisting its `widget` override to the top-level
+  form-field config, so a field with `widget: 'object-ref'` (or `filter-condition`
+  / `recipient-picker`) degraded to its bare `type` input — an admin was asked to
+  hand-type an object name instead of picking it. The form renderer now falls back
+  to the field metadata's own `widget` when no top-level override is present, so
+  the pickers render on sectioned forms just as they do on flat ones.
+- Updated dependencies [443360a]
+- Updated dependencies [c70bca7]
+- Updated dependencies [86c69c3]
+- Updated dependencies [05e56ca]
+- Updated dependencies [5971cc4]
+- Updated dependencies [6a74160]
+  - @object-ui/core@14.0.0
+  - @object-ui/i18n@14.0.0
+  - @object-ui/react@14.0.0
+  - @object-ui/types@14.0.0
+  - @object-ui/react-runtime@14.0.0
+  - @object-ui/sdui-parser@14.0.0
+
+## 13.2.0
+
+### Patch Changes
+
+- 80901aa: Honor action `visible` (and `enabled`) predicates in three more action renderers.
+
+  Following the data-table row-action fix, three sibling renderers still rendered schema-defined actions without evaluating their `visible` CEL predicate:
+
+  - **`action:group` dropdown mode** (`@object-ui/components`) — dropdown items ignored `visible`/`enabled`, while the group's inline mode already honored them.
+  - **Related-list `list_toolbar` header actions** (`@object-ui/plugin-detail`) — e.g. an organization's "Invite User" button ignored `visible`, even though the sibling row actions (fed by the same `deriveActions` bridge) already honored it via the data-table's `DataTableRowActionItem`.
+  - **Grid bulk-action bar** (`@object-ui/plugin-grid`) — `bulkActionDefs.visible` was ignored entirely; the button is now hidden when the predicate is false (the `BulkActionDef.visible` doc comment is corrected from "disables" to "hides" to match).
+
+  Each now evaluates `visible` (and, where applicable, `enabled`) via a hook-safe per-item component that mirrors `RowActionMenuItem` / `DataTableRowActionItem`, resolving `features`/`user` from the ambient `ExpressionProvider` scope. Rendering-layer only — no action definitions changed.
+
+- e492b9d: Permission sets — pure separation of **design** (Studio) and **assignment**
+  (Setup), per ADR-0056 / epic #2398. A `sys_permission_set` used to render its six
+  authorization facets in Setup as raw `[Object]` / JSON textareas, and only
+  objects+fields were editable in Studio; this reworks both surfaces.
+
+  **Setup (assign + read-only):**
+  - The six facets (`object_permissions`, `field_permissions`, `system_permissions`,
+    `row_level_security`, `tab_permissions`, `admin_scope`) now render read-only on
+    the `sys_permission_set` record page as a compact summary (counts, or capability
+    chips) plus a **“Design in Studio →”** deep-link into the structured editor
+    (`/apps/:appName/metadata/permission/:setName`, env scope). No `[Object]`, no
+    JSON — in the record view, inline edit, and the create/edit form. Implemented as
+    a `permission-facet-link` field widget stamped onto the six fields via the single
+    `ObjectStackAdapter.getObjectSchema` choke point and honored by DetailSection +
+    the record form.
+  - User assignment (add/remove via `sys_user_permission_set`) is surfaced directly
+    on the Setup record page.
+
+  **Studio (design every facet):** the permission matrix editor gains structured
+  editors for the facets that were JSON-only —
+  - **System Capabilities**: a multi-select over the live `sys_capability` registry
+    (scope-grouped, labelled chips).
+  - **Row-Level Security**: per-policy rows (object · operation · enabled) with CEL
+    USING/CHECK.
+  - **Tab Visibility**: per-tab `visible | hidden | default_on | default_off`.
+  - **Delegated Admin Scope**: business-unit + subtree, manage-assignments /
+    -bindings / author-env-sets toggles, and an assignable-permission-sets allowlist.
+    Assignment was moved out of the editor (it is now a Setup act) — the editor is
+    purely a design surface.
+
+  Storage/types are unchanged; editors read/write the draft’s existing parsed
+  fields and tolerate legacy JSON strings on load. Note: env-scope metadata saves of
+  these facets do not yet project onto the queryable `sys_permission_set` data
+  record the Setup summary reads, so a fresh Studio edit isn’t reflected in Setup’s
+  read-only view until the projection refreshes — tracked as a framework follow-up
+  (enforcement reads the authoritative metadata).
+
+- Updated dependencies [53c40c2]
+  - @object-ui/i18n@13.2.0
+  - @object-ui/react@13.2.0
+  - @object-ui/types@13.2.0
+  - @object-ui/core@13.2.0
+  - @object-ui/react-runtime@13.2.0
+  - @object-ui/sdui-parser@13.2.0
+
 ## 13.1.0
 
 ### Patch Changes