Skip to content

docs(skills): objectstack-data teaches relatedList placement by each value’s role, not by record-page tabs or columns #29929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 1 commit into from
Nov 3, 2026
Merged

docs(skills): objectstack-data teaches relatedList placement by each value’s role, not by record-page tabs or columns #29929

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .changeset/29801-related-list-placement-skill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
'@objectstack/skills': patch
---

docs(skills): objectstack-data teaches `relatedList` placement by each value's role, not by record-page tabs or columns

Clause-②: no
Metadata-protocol: none

- **Before.** `rules/relationships.md` said `relatedList: 'primary'` draws "a full-width table in the details column after the first field section (in the Details tab, no tab of its own)" and that `true` / omitted is "a side card (the shared **Related** tab)". The spec's `relatedList` describe no longer names any tab or column, so the skill taught a page layout the record page does not draw.
- **Now.** The three bullets follow the spec describe: `'primary'` is part of the record's main content, a full-width table in the record's detail body (still the default for an inline-edited `master_detail` FK); `false` means the child object is not shown on the parent record page; `true` or omitted is an auxiliary panel on the record page. Layout stays ADR-0085's to define.
- The file gets smaller and stays under its token ceiling; no ceiling moves, no schema, key or behaviour changes.
11 changes: 5 additions & 6 deletions skills/objectstack-data/rules/relationships.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,12 +335,11 @@ audit_ref: { type: 'master_detail', reference: 'invoice', relatedList: false },

`relatedList` is tri-state — placement (ADR-0085):

- `'primary'` — main content: a full-width table in the details column after
the first field section (in the Details tab, no tab of its own). Default for a
`master_detail` FK with `inlineEdit`.
- `false` — hidden from the parent's page.
- `true`, or omitted (except inline-edited `master_detail`) — a side card
(the shared **Related** tab).
- `'primary'` — part of the record's main content: a full-width table in the
record's detail body. Default for a `master_detail` FK with `inlineEdit`.
- `false` — the child object is not shown on the parent record page.
- `true`, or omitted (except inline-edited `master_detail`) — an auxiliary
panel on the record page.
- Order is the parent's: `relatedLists: ['task', 'event.related_to']` (child, or
`object.field`) lists those first. A child in the stack with no inbound FK is
refused everywhere; one that exists nowhere is refused by `os validate` /
Expand Down
Loading