Uh oh!
There was an error while loading. Please reload this page.
feat(app-shell): detail.hidePath opt-out for the auto record:path stepper - #2062
Closed
baozhoutao wants to merge 1 commit into
Closed
feat(app-shell): detail.hidePath opt-out for the auto record:path stepper#2062baozhoutao wants to merge 1 commit into
baozhoutao wants to merge 1 commit into
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This was referenced Jun 29, 2026
…pper
Surface the synth's existing `hidePath` option through
`objectDef.detail.hidePath`. Set `detail: { hidePath: true }` to suppress the
auto-prepended Lightning Path-style status stepper on a record detail page.
Useful when the auto-detected status picklist is not a linear pipeline — e.g. a
field that folds a risk gradient into the status (已完成 / 进行中-低风险 …
进行中-特高风险 / 已逾期), where the stepper marks earlier options as
'completed' purely by list position and misrepresents the record. Default
(unset) keeps the stepper — zero regression.
Mirrors the existing detail.hideRelatedTab / relatedLayout wiring; the synth
side (option + buildHeaderRegion consumption + unit tests) already exists.
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.
What
Surface the synth's existing
hidePathoption throughobjectDef.detail.hidePath:One-line wiring in
RecordDetailView.tsx, mirroring the existingdetail.hideRelatedTab/detail.relatedLayoutmappings. Default (unset) keeps the stepper — zero regression.Why
The record detail page auto-detects a "status/stage" field (
detectStatusField) and renders it as a Salesforce Lightning Path-style stepper at the top, marking every option before the current value as "completed ✓" — purely by list position.That's correct for a genuine linear pipeline, but wrong when the picklist isn't one. Real-world example: a
任务状态field that folds a risk gradient into the status —The stepper then checks off
已完成and every lower-risk state as "done" just because they sort earlier, which misrepresents the record. Until the data model is split (status vs. risk), authors need a config-level off switch.detail.hidePathis that switch.This is the opt-out half; a follow-up may tighten auto-detection (only emit a path for an explicit
stage-typed field /stageField), but that changes a global default and is out of scope here.Scope
packages/app-shell/src/views/RecordDetailView.tsx— passhidePathfromobjectDef.detail.hidePath.@object-ui/app-shellminor.hidePath(option +buildHeaderRegionconsumption + unit tests) already exists.Verification
turbo type-check --filter=@object-ui/app-shell→ 28 tasks passbuildDefaultPageSchema.test.ts→ 54 pass (incl.hidePathcases)no-emptyerror (unrelated) + repo-wideanywarnings