feat: related-list 'primary' tabs, multi-FK & self-ref, unified picker columns (framework #2579)#2235
Merged
Merged
Conversation
…lti-FK & self-ref, unified picker columns (framework #2579) - buildDefaultTabs: default is now the ADR-0085 prominence rule — `relatedList: 'primary'` lists each get their own tab, the rest collapse into one "Related" tab (no primary anywhere → byte-for-byte the legacy stacked default). `relatedLayout: 'tabs' | 'stack'` remain app-level overrides. - deriveRelatedLists: one related list per eligible FK (multi-FK children), self-referential relationships (hierarchies), and carries the isPrimary flag through; RecordDetailView threads it into the synthesized page. - RelatedList + deriveLookupColumns: auto-derived columns prefer the object's highlightFields — the same "how to list this object" source — so a related list and a lookup picker of the same object agree with zero per-surface config. Pairs with the @objectstack/spec tri-state `relatedList` + optional related-list `columns` change. 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
|
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 free
to 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
Renderer + derivation for detail-page related-list tabs — companion to the spec change in objectstack-ai/framework#2594, for framework issue objectstack-ai/framework#2579.
buildDefaultTabs(plugin-detail): the default related-list layout is now the ADR-0085 prominence rule — lists whose FK declaresrelatedList: 'primary'each get their own tab; every other related list collapses into a single "Related" tab. With no'primary'anywhere this is byte-for-byte the previous stacked default (opt-in per relationship).relatedLayout: 'tabs' | 'stack'remain app-level overrides (force all-own-tabs / all-stacked).deriveRelatedLists(app-shell): emits one related list per eligible FK — a child referencing the parent through several relationships (e.g.primary_account+partner_account) now surfaces each, disambiguated by the FK label; includes self-referential relationships (hierarchies → a "child" list); and carries theisPrimaryflag through.RecordDetailViewthreads it into the synthesized page.RelatedList+deriveLookupColumns: auto-derived columns prefer the object'shighlightFields— the same "how to list this object" source — so a related list and a lookup picker of the same object agree with zero per-surface config.Companion PR
Spec (tri-state
relatedList, optional related-listcolumns): objectstack-ai/framework#2594.Verification
buildDefaultTabsrule Z +RelatedListcolumn derivation).deriveLookupColumnshighlightFields priority).deriveRelatedLists: 15 tests pass (multi-FK, self-ref, primary).Refs objectstack-ai/framework#2579.
🤖 Generated with Claude Code