Uh oh!
There was an error while loading. Please reload this page.
Detail view: Edit as primary CTA; enter inline edit by double-clicking a field (#2401) - #2402
Merged
Merged
Conversation
… by double-clicking a field (#2401) Replace the standalone "Edit fields" inline-edit toggle with a per-field affordance: hovering a field reveals a pencil and double-clicking it (or the pencil) flips the record into inline edit — focused on that field — with the existing Save/Cancel bar. The header now shows a single primary Edit button (full form); Share/Delete fall into the overflow menu. Mirrors Salesforce. - RecordDetailView: drop the sys_inline_edit header action so sys_edit becomes the primary CTA (page:header overflow keeps Share/Delete). - DetailView: remove the idle standalone toggle and the mobile inline-edit entry; the Save/Cancel bar renders only while editing; add handleEnterInlineEditField + autoFocusField and thread onEnterInlineEdit to every section. - DetailSection: hover pencil + double-click enter edit; gate the affordance and the input on field editability (skip computed formula/summary/rollup/ auto_number and readonly fields); auto-focus the entered field. - record-details: gate inline editability by object lifecycle (managedBy / userActions) so double-click isn't offered on system/append-only objects — the gate the removed sys_inline_edit carried. - i18n: add detail.editInlineHint (en/zh) + DETAIL_DEFAULT_TRANSLATIONS fallback. - test: DetailSection double-click affordance + computed/readonly gating (5 cases). Closes#2401 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jul 13, 2026
os-zhuang added a commit
that referenced
this pull request
Jul 13, 2026
… fields (#2402 hardening) (#2408) The double-click / pencil inline-edit affordance from #2402 only gated on the VIEW schema's `readonly` + computed types. It ignored (a) the OBJECT metadata's `readonly` flag — the field enrichment deliberately doesn't copy it — and (b) immutable system/audit fields by name. So a field the object schema marks read-only, or a `created_at` surfaced as a section row, could be double-clicked into an editor. - DetailSection: `fieldEditable` now also excludes `objectDefField.readonly` and a new `NON_EDITABLE_SYSTEM_FIELDS` name set. - New `systemFields.ts`: the immutable-fields set — deliberately NARROWER than the display-oriented sets in deriveLookupColumns/RecordDetailDrawer (excludes owner/tenant/org, which are legitimately editable in some contexts). - Tests: object-schema-readonly and system fields are not inline-editable; normal fields still are. Refs #2402 Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes#2401.
What & why
The record header exposed two competing edit entry points — a prominent
Edit fields(the inline-edit toggle) and a buriedEdit(full form) — an inconsistent, confusing hierarchy (worse in thepage:headersynth path, where the overflow logic pushed the primaryEditinto the…menu). This collapses them into one clear model (Salesforce-style):Editis the single primary CTA in the header (opens the full form). Share/Delete live in the…overflow.Edit fieldstoggle.Single-click stays for text-selection/copy (these are read-oriented display fields with selectable emails/links), so double-click + hover-pencil is the right trigger.
Changes
RecordDetailViewsys_inline_editheader action →sys_editbecomes the primary button; overflow keeps Share/Delete.DetailViewhandleEnterInlineEditField+autoFocusField; threadonEnterInlineEditto every section.DetailSectionrecord-detailsmanagedBy/userActions) — the gate the removedsys_inline_editbutton used to carry.i18ndetail.editInlineHint(en/zh) +DETAIL_DEFAULT_TRANSLATIONSfallback.Guardrails preserved
formula/summary/rollup/auto_number) andreadonlyfields expose no pencil and never become inputs — even in global inline-edit mode.system/append-only/better-authobjects (honorsuserActions.edit).{ [field]: value }stays the de-facto sanitizer — no full-record writes).Verification
plugin-detail(vite) build ✓,app-shell(tsc) build ✓,i18n(tsc) build ✓.DetailSection.doubleClickEdit.test.tsx, 5 cases) + existing DetailView/record-details suites: 129 passing.Projectrecord pending (dev-server login).🤖 Generated with Claude Code