Uh oh!
There was an error while loading. Please reload this page.
feat(master-detail): derive child columns + FK from metadata - #1526
Merged
Conversation
A master-detail child collection can be configured with just { childObject }.
The relationship FK is auto-detected from the child's master_detail/lookup
field referencing the parent, and grid columns are derived from the child
object schema (skipping system/audit/FK/non-editable fields; select options
+ lookup refs carried through). amountField defaults to the first numeric
column. Explicit relationshipField/columns still override.
New pure helpers deriveDetail/deriveColumns/findRelationshipField (+9 unit
tests, 76 plugin-form pass). MasterDetailForm resolves unconfigured details
via getObjectSchema and gates Save until resolved.
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 was referenced Jun 6, 2026
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.
Summary
Answers "do master-detail forms really need a hand-authored columns block?" — no. A child collection can now be configured with just the child object name; the relationship FK and editable grid columns are derived from the child object's metadata.
What it does
relationshipFieldauto-detected from the child'smaster_detail/lookupfield whosereferenceis the parent (master_detail preferred).columnsderived from the child's fields — skips system/audit fields, the back-reference FK, and non-editable types (formula/summary/autonumber/file/json/…); selectoptionsand lookupreference/displayFieldcarry through; types mapped to grid column types.amountField(running-total source) defaults to the first numeric/currency column.MasterDetailFormresolves unconfigured details viagetObjectSchemaand gates Save until resolved.Testing
deriveDetail/deriveColumns/findRelationshipField+fieldTypeToColumnType— 9 unit tests (76 plugin-form pass)./api/v1/batch(parent + child{$ref:0}). Paired showcase simplification in the framework repo drops itsdetailsblock to one line.🤖 Generated with Claude Code