@object-ui/plugin-detail 4.4.0 → 4.6.0

package/CHANGELOG.md

@@ -1,5 +1,41 @@
 # @object-ui/plugin-detail
 
+## 4.6.0
+
+### Patch Changes
+
+- 8f490ad: test(perms): add field-level permission negative tests for DetailView
+  and ListView. Mounts each consumer inside a `PermissionProvider` that
+  denies read on a specific field and asserts the field never reaches
+  the rendered DOM (sections, top-level fields, summary chips,
+  constructed list columns). Closes the automated half of the Sprint 3-A
+  "Known limitations" — backend enforcement is still required, but the
+  client-side defence-in-depth is now regression-tested.
+
+## 4.5.0
+
+### Minor Changes
+
+- ab5e281: `record:highlights` renderer normalizes rich field items.
+
+  `RecordHighlightsComponentProps.fields` is now `Array<string | { name, label?, icon?, type? }>`. The renderer normalizes both forms before passing to `HeaderHighlight`, so schemas can attach per-instance label/icon overrides without editing the underlying object metadata. FLS and `redactFields` still apply on the normalized list.
+
+### Patch Changes
+
+- d714e85: Lookup display-name resolution now falls back through a Salesforce-style chain
+  when an `$expand`'d reference object lacks a top-level `name`/`label`/
+  `display_name`/`title` field:
+  1. Standard display fields (existing behaviour)
+  2. `salutation first_name last_name` composite — handles person records that
+     only carry first/last name parts
+  3. `email` — last-resort identifier, beats the opaque id
+
+  Applies to `LookupCellRenderer`, `PageHeader.subtitle` interpolation,
+  `DetailView` page-mode `titleFormat`, and the shared `formatRecordTitle`
+  utility. Concretely: a Contact reference with `first_name: Bob`, `last_name:
+Lin` and no `name` field now renders as `Bob Lin` everywhere — instead of
+  the email or [object Object] fallback.
+
 ## 4.4.0
 
 ### Patch Changes