@object-ui/react 4.7.0 → 5.0.0

package/CHANGELOG.md

@@ -1,5 +1,123 @@
 # @object-ui/react
 
+## 5.0.0
+
+### Minor Changes
+
+- 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.
+
+- 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.
+
+- 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` → `备注与附件`).
+
+- 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.
+
+### Patch Changes
+
+- Updated dependencies [8930b15]
+- Updated dependencies [7213027]
+- Updated dependencies [c7561a7]
+  - @object-ui/i18n@5.0.0
+  - @object-ui/types@5.0.0
+  - @object-ui/data-objectstack@5.0.0
+  - @object-ui/core@5.0.0
+
+## 4.8.0
+
+### Patch Changes
+
+- @object-ui/types@4.8.0
+- @object-ui/core@4.8.0
+- @object-ui/i18n@4.8.0
+- @object-ui/data-objectstack@4.8.0
+
 ## 4.7.0
 
 ### Patch Changes

package/dist/context/DiscussionContext.d.ts

@@ -0,0 +1,37 @@
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * DiscussionContext — shared chatter / discussion feed for the current
+ * record. Mounted alongside RecordContext by the host record page (see
+ * `RecordDetailView` in `@object-ui/app-shell`) so that any `record:chatter`
+ * or `record:discussion` renderer placed inside the schema tree picks up
+ * the same feed items / mutation handlers without a parallel fetch.
+ *
+ * Why this is separate from RecordContext: chatter feeds are commonly
+ * absent (e.g. settings pages, dashboards), and many record pages opt in
+ * via schema rather than always paying the fetch cost. Keeping the
+ * discussion data in its own context lets non-record pages provide it
+ * cheaply and lets record pages omit it without affecting unrelated
+ * record-aware renderers.
+ */
+import React from 'react';
+export interface DiscussionFeedItem {
+    id: string;
+    /** Generic discriminator — chatter renderers may switch on this. */
+    type?: string;
+    [k: string]: any;
+}
+export interface DiscussionContextValue {
+    items: DiscussionFeedItem[];
+    onAddComment?: (text: string, attachments?: any[]) => void | Promise<void>;
+    onAddReply?: (parentId: string, text: string) => void | Promise<void>;
+    onToggleReaction?: (itemId: string, reaction: string) => void | Promise<void>;
+    loading?: boolean;
+    error?: Error | null;
+}
+export interface DiscussionContextProviderProps extends DiscussionContextValue {
+    children: React.ReactNode;
+}
+export declare const DiscussionContextProvider: React.FC<DiscussionContextProviderProps>;
+export declare function useDiscussionContext(): DiscussionContextValue | null;

package/dist/context/DiscussionContext.js

@@ -0,0 +1,34 @@
+import { jsx as _jsx } from "react/jsx-runtime";
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * DiscussionContext — shared chatter / discussion feed for the current
+ * record. Mounted alongside RecordContext by the host record page (see
+ * `RecordDetailView` in `@object-ui/app-shell`) so that any `record:chatter`
+ * or `record:discussion` renderer placed inside the schema tree picks up
+ * the same feed items / mutation handlers without a parallel fetch.
+ *
+ * Why this is separate from RecordContext: chatter feeds are commonly
+ * absent (e.g. settings pages, dashboards), and many record pages opt in
+ * via schema rather than always paying the fetch cost. Keeping the
+ * discussion data in its own context lets non-record pages provide it
+ * cheaply and lets record pages omit it without affecting unrelated
+ * record-aware renderers.
+ */
+import React from 'react';
+const DiscussionContext = React.createContext(null);
+export const DiscussionContextProvider = ({ children, ...value }) => {
+    const memo = React.useMemo(() => value, [
+        value.items,
+        value.onAddComment,
+        value.onAddReply,
+        value.onToggleReaction,
+        value.loading,
+        value.error,
+    ]);
+    return (_jsx(DiscussionContext.Provider, { value: memo, children: children }));
+};
+export function useDiscussionContext() {
+    return React.useContext(DiscussionContext);
+}

package/dist/context/RecordContext.d.ts

@@ -13,6 +13,17 @@
  * receive props from the schema tree.
  */
 import React from 'react';
+export declare const HighlightFieldsProvider: React.FC<{
+    children: React.ReactNode;
+}>;
+/** Subscribe to the live highlight-field set. Empty when no provider. */
+export declare function useHighlightFieldNames(): ReadonlySet<string>;
+/**
+ * Register a list of field names as currently surfaced by a
+ * `record:highlights` instance. Re-registers when the joined name list
+ * changes; unregisters on unmount.
+ */
+export declare function useRegisterHighlightFields(instanceId: string, names: string[]): void;
 export interface RecordContextValue<TData = any, TObjectSchema = any> {
     /** Object machine name, e.g. "crm_opportunity". */
     objectName: string;
@@ -30,6 +41,16 @@ export interface RecordContextValue<TData = any, TObjectSchema = any> {
     error?: Error | null;
     /** Re-fetch the record from the source. */
     refresh?: () => void | Promise<void>;
+    /**
+     * Optional system-level header actions (Edit / Share / Delete) that the
+     * host (e.g. RecordDetailView) wants to inject into the page header
+     * regardless of whether the page schema is synthesised or authored.
+     *
+     * `PageHeaderRenderer` appends these AFTER any authored
+     * `page:header.actions`, deduplicating by `name`. Hosts pass `undefined`
+     * to opt out entirely (e.g. embedded previews).
+     */
+    headerSystemActions?: any[];
     /**
      * When true, the record is rendered inside a host overlay (drawer,
      * modal, split-pane preview) rather than as a standalone route. Header

package/dist/context/RecordContext.js

@@ -14,6 +14,78 @@ import { jsx as _jsx } from "react/jsx-runtime";
  * receive props from the schema tree.
  */
 import React from 'react';
+const HighlightFieldsContext = React.createContext(null);
+export const HighlightFieldsProvider = ({ children }) => {
+    const registry = React.useMemo(() => {
+        const map = new Map();
+        let names = EMPTY_SET;
+        const listeners = new Set();
+        const recompute = () => {
+            const next = new Set();
+            for (const list of map.values())
+                for (const n of list)
+                    next.add(n);
+            // Skip notify if shallow-equal to previous (avoid spurious updates).
+            if (next.size === names.size) {
+                let same = true;
+                for (const n of next)
+                    if (!names.has(n)) {
+                        same = false;
+                        break;
+                    }
+                if (same)
+                    return;
+            }
+            names = next;
+            listeners.forEach((l) => l());
+        };
+        return {
+            getNames: () => names,
+            subscribe: (l) => {
+                listeners.add(l);
+                return () => { listeners.delete(l); };
+            },
+            register: (id, list) => {
+                const prev = map.get(id);
+                if (prev &&
+                    prev.length === list.length &&
+                    prev.every((n, i) => n === list[i])) {
+                    return;
+                }
+                map.set(id, [...list]);
+                recompute();
+            },
+            unregister: (id) => {
+                if (map.delete(id))
+                    recompute();
+            },
+        };
+    }, []);
+    return (_jsx(HighlightFieldsContext.Provider, { value: registry, children: children }));
+};
+/** Subscribe to the live highlight-field set. Empty when no provider. */
+export function useHighlightFieldNames() {
+    const ctx = React.useContext(HighlightFieldsContext);
+    return React.useSyncExternalStore(ctx ? ctx.subscribe : NOOP_SUBSCRIBE, ctx ? ctx.getNames : GET_EMPTY, ctx ? ctx.getNames : GET_EMPTY);
+}
+/**
+ * Register a list of field names as currently surfaced by a
+ * `record:highlights` instance. Re-registers when the joined name list
+ * changes; unregisters on unmount.
+ */
+export function useRegisterHighlightFields(instanceId, names) {
+    const ctx = React.useContext(HighlightFieldsContext);
+    const key = names.join('|');
+    React.useEffect(() => {
+        if (!ctx)
+            return;
+        ctx.register(instanceId, key.length === 0 ? [] : key.split('|'));
+        return () => ctx.unregister(instanceId);
+    }, [ctx, instanceId, key]);
+}
+const NOOP_SUBSCRIBE = (_) => () => { };
+const GET_EMPTY = () => EMPTY_SET;
+const EMPTY_SET = new Set();
 const RecordContext = React.createContext(null);
 export const RecordContextProvider = ({ children, ...value }) => {
     // Memoize so consumers that rely on referential equality don't re-render
@@ -28,6 +100,7 @@ export const RecordContextProvider = ({ children, ...value }) => {
         value.error,
         value.refresh,
         value.embedded,
+        value.headerSystemActions,
     ]);
     return _jsx(RecordContext.Provider, { value: memo, children: children });
 };

package/dist/context/index.d.ts

@@ -5,3 +5,4 @@ export * from './NotificationContext';
 export * from './DndContext';
 export * from './AppShellContext';
 export * from './RecordContext';
+export * from './DiscussionContext';

package/dist/context/index.js

@@ -5,3 +5,4 @@ export * from './NotificationContext';
 export * from './DndContext';
 export * from './AppShellContext';
 export * from './RecordContext';
+export * from './DiscussionContext';

package/dist/hooks/usePageAssignment.d.ts

@@ -10,6 +10,14 @@
  * and returns the first PageSchema whose `pageType === 'record'` and `object`
  * matches the requested name.
  *
+ * Returns a discriminated result by `PageSchema.kind`:
+ *   - `kind === 'full'` (default): the schema fully describes the page;
+ *     the result populates `page` and the caller renders it as-is.
+ *   - `kind === 'slotted'`: the schema only provides slot overrides;
+ *     the result populates `slots` and the caller feeds them to
+ *     `buildDefaultPageSchema(objectDef, { slots })` so omitted slots
+ *     fall through to synthesized defaults.
+ *
  * Future work (deferred): recordType / profile / app / formFactor filtering
  * and priority-based selection. For now we return the first match so that
  * callers can deterministically fall back to the auto-generated DetailView
@@ -28,8 +36,24 @@ export interface PageAssignmentOptions {
     pageName?: string;
 }
 export interface PageAssignmentResult {
-    /** Resolved PageSchema, or null if no record Page is available. */
+    /**
+     * Resolved full PageSchema, or null when none is available.
+     *
+     * Populated only when the matched page has `kind === 'full'` (the
+     * default — see `PageSchema.kind`). Slotted pages do NOT populate
+     * this field; callers should branch on `slots` instead.
+     */
     page: any | null;
+    /**
+     * Slot override map for the matched slotted page, or null when no
+     * slotted page matched.
+     *
+     * Populated only when the matched page has `kind === 'slotted'`.
+     * The caller is expected to feed these slots to the default-page
+     * synthesizer (`buildDefaultPageSchema(objectDef, { slots })`) so
+     * that omitted slots fall through to synthesized defaults.
+     */
+    slots: any | null;
     /** True while the metadata cache is still loading the `page` type. */
     loading: boolean;
     /** Loader error, if any. */

package/dist/hooks/usePageAssignment.js

@@ -10,6 +10,14 @@
  * and returns the first PageSchema whose `pageType === 'record'` and `object`
  * matches the requested name.
  *
+ * Returns a discriminated result by `PageSchema.kind`:
+ *   - `kind === 'full'` (default): the schema fully describes the page;
+ *     the result populates `page` and the caller renders it as-is.
+ *   - `kind === 'slotted'`: the schema only provides slot overrides;
+ *     the result populates `slots` and the caller feeds them to
+ *     `buildDefaultPageSchema(objectDef, { slots })` so omitted slots
+ *     fall through to synthesized defaults.
+ *
  * Future work (deferred): recordType / profile / app / formFactor filtering
  * and priority-based selection. For now we return the first match so that
  * callers can deterministically fall back to the auto-generated DetailView
@@ -54,7 +62,7 @@ export function usePageAssignment(objectName, opts = {}) {
             cancelled = true;
         };
     }, [meta]);
-    const page = useMemo(() => {
+    const matched = useMemo(() => {
         if (!objectName && !opts.pageName)
             return null;
         const pages = Array.isArray(meta.pages) ? meta.pages : [];
@@ -87,8 +95,20 @@ export function usePageAssignment(objectName, opts = {}) {
         candidates.sort((a, b) => (b?.priority ?? 0) - (a?.priority ?? 0));
         return candidates[0];
     }, [meta.pages, objectName, opts.pageName, opts.recordType, opts.profile, opts.app, opts.formFactor]);
+    // Discriminate by `kind`: full pages populate `page`, slotted pages
+    // populate `slots`. Missing `kind` defaults to 'full' for backwards
+    // compatibility with pre-Phase-I metadata.
+    const { page, slots } = useMemo(() => {
+        if (!matched)
+            return { page: null, slots: null };
+        if (matched.kind === 'slotted') {
+            return { page: null, slots: matched.slots ?? {} };
+        }
+        return { page: matched, slots: null };
+    }, [matched]);
     return {
         page,
+        slots,
         loading: meta.loading || !ensured,
         error: ensureError ?? meta.error ?? null,
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/react",
-  "version": "4.7.0",
+  "version": "5.0.0",
   "type": "module",
   "license": "MIT",
   "description": "React bindings and SchemaRenderer component for Object UI",
@@ -26,10 +26,10 @@
   "dependencies": {
     "@objectstack/spec": "^4.0.5",
     "react-hook-form": "^7.76.0",
-    "@object-ui/core": "4.7.0",
-    "@object-ui/data-objectstack": "4.7.0",
-    "@object-ui/i18n": "4.7.0",
-    "@object-ui/types": "4.7.0"
+    "@object-ui/core": "5.0.0",
+    "@object-ui/data-objectstack": "5.0.0",
+    "@object-ui/i18n": "5.0.0",
+    "@object-ui/types": "5.0.0"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",