@object-ui/plugin-detail 4.8.0 → 5.0.1

package/CHANGELOG.md

@@ -1,5 +1,388 @@
 # @object-ui/plugin-detail
 
+## 5.0.1
+
+## 5.0.0
+
+### Major Changes
+
+- bb2ea48: **Phase O.0 — fix: related-list shows wrong records (critical data bug)**
+
+  `RelatedList` previously called `dataSource.find(api)` with no filter
+  when auto-fetching, so every Related tab dumped the entire target
+  object table instead of the records that actually reference the
+  current parent (e.g. an Account showed every Contact in the system,
+  not only contacts of that account).
+
+  Two coupled fixes:
+  1. `RelatedList` now requires `parentId` + `referenceField` to auto-
+     fetch. When both are present it calls `dataSource.find(api,
+{ $filter: { [referenceField]: parentId } })`. When either is
+     missing it renders the empty state and logs a developer warning —
+     never silently fetches the whole object.
+  2. `RelatedCountStore` was sending the probe query as `{ where, limit }`
+     which most data-source adapters silently ignored (the codebase
+     convention is `{ $filter, $top }`). The tab-count badges were
+     therefore showing the global object count, not the parent-scoped
+     count. Switched to `$filter` / `$top` to match.
+
+  `record:related_list` renderer threads `ctx.recordId` through as
+  `parentId`; no schema author changes required.
+
+  **Breaking:** custom callers that depended on `RelatedList` fetching
+  the entire object table when `referenceField` is omitted will need to
+  either pass `data` explicitly or supply both `parentId` and
+  `referenceField`. The previous behaviour was a bug, not a feature.
+
+### Minor Changes
+
+- 542cca9: feat(detail): buildDefaultPageSchema synthesizer (Track 3 Phase G slice 1)
+
+  Pure-function synthesizer that emits a canonical Lightning-style Page
+  schema (`page:header` → `record:highlights?` → `record:path?` →
+  `page:tabs` → `record:discussion?`) from an object definition and
+  optional overrides. Also exports helpers `detectStatusField`,
+  `deriveStages`, `deriveHighlightFields`.
+
+  This is the foundation for converging the default `<DetailView>`
+  output with custom Lightning pages. Phase H will wire it into
+  `RecordDetailView`'s non-assignedPage branch so the default detail
+  page renders through the same `<SchemaRenderer>` pipeline as custom
+  pages, inheriting all Phase D/E/F polish automatically.
+
+  No runtime behaviour change in this slice — synthesizer is exported
+  but not yet consumed.
+
+- 8930b15: feat(detail): close the gap between Page-assigned and default record detail pages (Track 1)
+
+  Custom Lightning-style record detail pages (assigned via `assignedPage` /
+  `Page` schemas) used to feel meaningfully poorer than the auto-generated
+  default detail view. They were missing cross-cutting affordances and
+  shipped with English-only tab labels and heavy bordered section cards
+  even when the host locale was Chinese. Track 1 closes the visible gap:
+  - **app-shell `RecordDetailView`**: the `assignedPage` branch now wears
+    the same chrome as the default branch — lifecycle managed-by badge
+    and presence avatars in the top-right, `MetadataPanel` debug panel,
+    `ActionConfirmDialog` / `ActionParamDialog`, and an auto-appended
+    `RecordChatterPanel` at the bottom of the page. Authors opt out of
+    the auto-discussion with `assignedPage.disableDiscussion = true`.
+  - **plugin-detail `record:details`**: defaults to `inlineEdit: true` so
+    fields are click-to-edit just like the default page, and synthesises
+    sections with `showBorder: false` by default so a Lightning page
+    doesn't double-wrap every block in a heavy Card.
+  - **components `page:tabs` / `page:accordion`**: well-known English
+    labels (Details / Related / Activity / History / Notes / Files /
+    Tasks / Events / Attachments / Chatter / Discussion / Comments /
+    Overview / Summary) auto-translate to Chinese (`zh-CN` / `zh-TW`)
+    via a built-in dictionary keyed off `document.documentElement.lang`.
+    Authors supplying explicit localised labels (string or
+    `{ default, zh-CN, ... }`) are not affected.
+  - **i18n provider**: applies the initial language to
+    `document.documentElement.lang` on mount (i18next does not fire
+    `languageChanged` for the bootstrap language), so locale-aware
+    renderers downstream see the right value from the first render.
+
+- 927187a: Phase N.1 + N.2: visual polish for record detail pages.
+
+  **N.1 — System actions on full Lightning pages.** `PageHeaderRenderer`
+  now merges `headerSystemActions` from `RecordContext` with authored
+  actions (authored wins on name/id collision), so full custom pages
+  (lead, opportunity, ...) once again show 编辑 / 分享 / 删除 alongside
+  their authored actions. `sys_share` and `sys_delete` now use the
+  `outline` variant instead of `destructive` to read better in
+  multi-button clusters.
+
+  **N.2 — Hide empty fields by default in synth detail pages.**
+  `record:details` defaults `section.hideEmpty` to `true` so synthesized
+  pages don't render label graveyards on first load. The "显示 N 个空字段"
+  reveal toggle is preserved as the user-facing escape hatch. Authors can
+  opt back into showing every field by setting `hideEmpty: false` on the
+  section schema.
+
+- bae8ba8: Phase N.3 + N.4 + N.6: record detail visual polish.
+
+  **N.3 — Highlight strip packs left.** `HeaderHighlight` no longer
+  stretches a 1-2 chip strip across the full page. Each cell is now
+  `min-w-[8rem] max-w-[16rem]` and wraps via flexbox so sparse strips
+  sit naturally at the left edge.
+
+  **N.4 — De-duplicate highlight ↔ body.** `record:details` accepts a
+  new `hideFields: string[]` prop. The synth pipeline auto-populates it
+  with the highlight-strip field list so a field surfaced in
+  `record:highlights` no longer appears a second time in the section
+  grid below. Authors can also set it directly on the schema.
+
+  **N.6 — Tab count badges only show when >0.** `page:tabs` suppresses
+  the count pill when the count is exactly 0 (was rendering "0" as a
+  muted badge on every empty Activity/History tab).
+
+- 8435860: Phase N.4b: highlight↔body dedup now works for hand-authored Lightning
+  pages too.
+
+  Adds a small `HighlightFieldsContext` registry. `record:highlights`
+  registers the field names it currently surfaces; `record:details` unions
+  that live set into its `hideFieldNames` filter so a field shown in the
+  highlight strip is never duplicated in the section grid below.
+
+  Previously the dedup only fired for synth-generated pages (via the
+  `hideFields` prop passed by `buildDefaultPageSchema`). Custom Lightning
+  pages (e.g. opportunity) showed `所属客户` both in the strip and in the
+  body. The registry-based approach covers both code paths uniformly with
+  no schema author work required.
+
+  The registry uses `useSyncExternalStore` so adding/removing highlights
+  notifies consumers without triggering the provider value identity to
+  change — avoiding the update-loop that a naive context implementation
+  would cause.
+
+  `RecordDetailView` mounts `<HighlightFieldsProvider>` once per record
+  page so the two renderers share state.
+
+- bece8ca: Phase N (continued): merge custom record_header actions into `page:header`
+  instead of emitting a sibling `record:quick_actions` node. This fixes a
+  visual collision on objects (contact, account, ...) that author custom
+  record_header actions: previously the floating quick-actions bar
+  (`-mt-12` overlay) collided with the system Edit/Share/Delete cluster
+  already rendered by `page:header`. Now all action buttons live on a single
+  header row.
+
+  `buildDefaultHeader` accepts an optional `actions` array; `buildDefaultActions`
+  remains exported as a sub-builder for authors who explicitly want the
+  floating quick-action bar via a slot override.
+
+- 77c1877: **Phase O.1 — Cap detail body grid at 2 columns for denser, more legible layout.**
+
+  The auto-layout previously emitted **3 columns** for sections with 11+
+  fields, which on typical desktop widths produced very sparse rows
+  (label/value cells filled ~30% of each column, lots of whitespace).
+  Capped the inferred maximum at 2 columns so paired fields read as
+  cleanly-aligned label/value pairs.
+
+  Authors who explicitly set `section.columns: 3` retain the 3-column
+  layout — only the auto-inference default changed.
+
+- b14fe09: Phase P.0 + P.5: tighten record-detail header chrome.
+  - `RecordTitleChip` collapses the title row to a single baseline-aligned line — H1, eyebrow object label, copy-id, favorite star — instead of the previous two-row title + subtitle layout.
+  - `record:details` extends the highlight-field dedup set to also exclude the title field resolved from `objectSchema.primaryField` (or the standard `name`/`full_name`/`title`/`subject`/`display_name`/`label` fallbacks). Removes the duplicate row that previously echoed the H1 (e.g. "客户名称: Acme Corporation") inside the field grid.
+
+- 1911d34: **Phase P.1 — Collapse empty Related-list cards to header-only.**
+
+  Previously each empty related list rendered a full Card with a 200px+
+  "暂无相关记录" empty-state block (header + 32px icon + label +
+  optional CTA). With 5-10 related objects mostly empty (common on
+  fresh records), the Related tab became a wall of empty cards
+  spanning 1500+ vertical pixels.
+
+  Now: when a related list has zero records (and isn't loading), the
+  CardContent is skipped entirely. The header row shows the title +
+  `(0)` badge + an inline italic "暂无相关记录" hint + the `+ 新建`
+  button (downgraded to ghost variant). A 200px empty card becomes a
+  40px row.
+
+  Lists with data are unchanged.
+
+- ba98039: **Phase P.2 — Collapse CREATE event field-dump in History timeline.**
+
+  CREATE events render every populated field as a `from: — → to: value`
+  diff row. For a record with 20+ fields this turned the History tab
+  into a wall of debug-looking `Field: — → value` lines.
+
+  For `action === 'create'` we now render a single `▸ N fields
+populated` disclosure that expands on click. The expanded view shows
+  just `Field: value` (no useless `— →` arrow), since for a creation
+  event the "from" is implicitly empty.
+
+  UPDATE / DELETE events are unchanged — their field diffs are
+  genuinely informative.
+
+- 86c04f1: Phase Q: unify record-detail visual rhythm — one canvas, one box idiom.
+
+  Audit revealed three competing chrome treatments fighting on the same
+  page: the highlight strip was a filled Card, the discussion panel was
+  another filled Card, the related-list cards used heavy borders — while
+  the title chip, field grid, and history timeline were naked. The
+  result was visually noisy ("有的下划线，有的有边框，有的没边框").
+
+  This change commits to a single design language:
+  - **Highlights** (`HeaderHighlight`): drop the `Card`/`CardContent`
+    wrapper. Render as a borderless `<section>` of stat cells with a
+    subtle `border-b` separator. The tab strip below now carries the
+    only visible anchor in that vertical band.
+  - **Discussion / activity feed** (`RecordActivityTimeline`): drop the
+    `Card`/`CardHeader`/`CardContent` wrapper. Render as a borderless
+    `<section>` with a top divider and a semantic `<header>` for the
+    title. Right-side chatter panel still wraps with its own border so
+    no chrome is lost in pinned mode.
+  - **Related list** (`RelatedList`): keep the card grouping (each is a
+    table of child records — earned chrome), but tone it down to
+    `border-border/60 bg-transparent` so the boxes recede instead of
+    competing with the rest of the canvas.
+
+  Net effect: title / highlights / details / history sit on one
+  continuous bg-background canvas separated by whitespace + hairline
+  dividers; related lists are the one (subtle) boxed treatment, justified
+  by their tabular content. No internal package APIs changed.
+
+- 74962b0: feat(detail): record:discussion schema component + flush accordion variant
+  - New `record:discussion` schema type lets authors place the record
+    chatter feed anywhere in a custom Page schema. Wired through a
+    shared `DiscussionContext` provider on the `assignedPage` branch
+    of `RecordDetailView`; auto-append still applies when no explicit
+    `record:discussion` / `record:chatter` node is present.
+  - `page:accordion` gains a `variant` prop. Default `flush` strips the
+    per-item border so accordion sections no longer double-wrap inner
+    Card-bearing renderers (RelatedList, etc.). Authors who want the
+    old visual pass `variant: 'card'`.
+  - `translateLabel` now handles compound labels split by `&`, `and`,
+    or `和` (e.g. `Notes & Attachments` → `备注与附件`).
+
+- 8b850b5: feat(detail): record:path chevron stepper + record:highlights surface refresh (Phase E)
+  - `record:path` now renders Salesforce Lightning-style chevron segments
+    (clip-path arrows + overlap) with a primary glow on the current step
+    and a check mark on completed steps. On mobile (`<sm`) it falls back
+    to a horizontally-scrollable pill row that keeps the same semantics
+    but never overflows the viewport.
+  - `record:highlights` surface drops the dashed border in favour of a
+    solid `bg-muted/40` card with a softer border, so the highlights
+    strip reads as a continuous extension of the header chip above it
+    rather than a separate framed widget.
+
+- fa4c2cb: feat(detail): renderViaSchema opt-in routes default detail through SchemaRenderer (Track 3 Phase G slice 2)
+
+  When `?renderViaSchema=1` is in the URL, or `objectDef.detail.renderViaSchema === true`,
+  `RecordDetailView`'s no-assignedPage branch now synthesizes a canonical
+  Page schema (`page:header` → `record:highlights` → `record:path` →
+  `page:tabs(record:details)` → `record:discussion`) via
+  `buildDefaultPageSchema(objectDef, { sections, highlightFields })` and
+  renders it through the existing `<SchemaRenderer>` pipeline.
+
+  This means every object without a custom assigned page can opt in to
+  the same chrome (record-aware header chip, chevron path, flush
+  accordion, discussion slot) that custom Lightning pages already enjoy.
+
+  Changes:
+  - `buildDefaultPageSchema` now emits `page:tabs.items` (correct shape
+    for the renderer) rather than `tabs`.
+  - `PageHeaderRenderer.resolvedTitle` honors `objectSchema.primaryField`
+    before the legacy `name/title/display_name/label` fallbacks.
+  - `RecordDetailView` rebuilds the synthesized schema with
+    `detailSchema.sections` + `highlightFields` at render time so
+    `record:details` inherits the same field layout the legacy
+    `<DetailView>` would have produced.
+
+  Flag is intentionally off by default — flipping the default is a
+  separate explicit commit after empirical parity validation across
+  multiple objects. Known gaps tracked for slice 3: titleFormat
+  fallback for objects without `primaryField`, auto Activity / History
+  tabs, header-action buttons.
+
+- 7213027: feat(detail): slotted record pages (Track 3 Phase I)
+
+  Introduce `kind: "slotted"` record pages that override one or more
+  named slots while letting the default-page synthesizer fill in the
+  rest. Authors no longer need to re-author the entire page just to
+  customize the header or one tab.
+
+  **Slot menu (v1):**
+  - `header` — replaces `page:header`
+  - `actions` — replaces the `record:quick_actions` action bar
+  - `highlights` — replaces the chips + chevron path strip
+  - `details` — replaces the Details tab body (other tabs stay synthesized)
+  - `tabs` — replaces the entire `page:tabs` node (wins over `details`)
+  - `discussion` — replaces the inline `record:discussion` footer
+
+  Each slot is a full replacement at the slot boundary. To compose
+  default + custom, call the corresponding `buildDefault*` sub-builder
+  (now exported from `@object-ui/plugin-detail`):
+  `buildDefaultHeader`, `buildDefaultActions`, `buildDefaultHighlights`,
+  `buildDefaultDetails`, `buildDefaultTabs`, `buildDefaultDiscussion`.
+
+  **Author shape:**
+
+  ```ts
+  {
+    type: 'record',
+    object: 'account',
+    kind: 'slotted',
+    slots: {
+      header: { type: 'page:header', properties: { ... } },
+    },
+  }
+  ```
+
+  **API changes:**
+  - `PageSchema` (in `@object-ui/types`): adds `kind?: 'full' | 'slotted'`
+    (default `'full'`) and `slots?: PageSlotMap`.
+  - `usePageAssignment` (in `@object-ui/react`): result now exposes a
+    `slots` field populated when the matched page has `kind === 'slotted'`.
+    Existing `page` field is unchanged for full pages.
+  - `buildDefaultPageSchema` (in `@object-ui/plugin-detail`): accepts an
+    `options.slots` map that overrides individual regions at synthesis time.
+
+- 34b66bf: feat(detail): synthesize Related / Activity / History tabs + record:quick_actions header (Track 3 Phase G slice 4)
+  - `buildDefaultPageSchema` now accepts `headerActions`, `related`,
+    `showActivity`, and `history` options. When provided, the synthesizer
+    emits a `record:quick_actions` node after `page:header` and appends
+    the corresponding tabs to `page:tabs.items` in stable order
+    (Details / Related / Activity / History).
+  - New `record:history` renderer wraps the existing `HistoryTimeline`,
+    reading `entries` / `loading` from the schema. Host owns fetching.
+  - `RecordDetailView` forwards `detailSchema.actions[0].actions`,
+    `detailSchema.related[]` (unwrapped to `{objectName,relationshipField}`),
+    and `detailSchema.history` into the synthesizer call so the
+    `renderViaSchema` path reaches parity with the monolithic DetailView
+    tab strip and header action bar.
+  - 6 new unit tests covering headerActions emit/skip, Related tab
+    shape, Activity opt-in, History entries pass-through, and stable
+    tab ordering.
+
+  No behavior change for objects without the `renderViaSchema` opt-in.
+
+### Patch Changes
+
+- f16a762: feat(plugin-detail): cross-object detail-page convergence polish (Phase J)
+
+  Two regression fixes surfaced by the Phase J browser canary across CRM
+  record detail pages:
+  1. **`record:path` now localizes stage labels.** The renderer threads
+     `useSafeFieldLabel().translateOptions` against the record-context's
+     `objectName` + the schema's `statusField`, so picklist labels match the
+     active locale instead of leaking English (`New / Contacted / Qualified`)
+     onto zh-CN pages. Falls back to the schema's authored labels when no
+     i18n provider is mounted.
+  2. **`deriveHighlightFields` skips system + primary fields.** Adds
+     `organization_id`, `workspace_id`, `tenant_id`, `created_by`,
+     `updated_by`, `deleted_by` to the skip set so the synthesized highlight
+     strip stops leaking an orphan "CRM Test's Workspace" chip with no
+     visible field label. Also skips the object's `primaryField` and common
+     title-field candidates (`name`, `full_name`, `title`, `subject`,
+     `display_name`) so the strip never duplicates the page H1.
+
+  `ObjectDefLike` gains an optional `primaryField` declaration to drive the
+  new skip behavior. No spec changes; the field is already part of the
+  upstream object schema.
+
+- Updated dependencies [8930b15]
+- Updated dependencies [95b6b21]
+- Updated dependencies [ddb08a7]
+- Updated dependencies [765d50f]
+- Updated dependencies [927187a]
+- Updated dependencies [bae8ba8]
+- Updated dependencies [8435860]
+- Updated dependencies [bb2ea48]
+- Updated dependencies [b14fe09]
+- Updated dependencies [a7bef6e]
+- Updated dependencies [74962b0]
+- Updated dependencies [3154334]
+- Updated dependencies [fa4c2cb]
+- Updated dependencies [7213027]
+  - @object-ui/components@5.0.0
+  - @object-ui/react@5.0.0
+  - @object-ui/types@5.0.0
+  - @object-ui/fields@5.0.0
+  - @object-ui/core@5.0.0
+  - @object-ui/permissions@5.0.0
+
 ## 4.8.0
 
 ### Minor Changes