Uh oh!
There was an error while loading. Please reload this page.
feat(form): inline master-detail in a plain ObjectForm via subforms - #1527
Merged
Conversation
ObjectFormSchema.subforms: when set, a plain object-form delegates to
MasterDetailForm (parent fields + child grids, atomic save) — master-detail
by config, no bespoke page. Each subform needs only { childObject }
(FK + columns auto-derived). +1 unit test (77 plugin-form pass); types +
plugin-form build clean (no circular-import issue with the mutual
ObjectForm<->MasterDetailForm render reference).
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
Completes the "master-detail without a bespoke page" story.
ObjectFormSchemagains asubformsarray; when present, a regularobject-formrenders as a master-detail form (object fields on top, an editable child grid per collection, persisted together in one atomic transaction) by delegating toMasterDetailForm.Each subform needs only
childObject— the relationship FK and grid columns are derived from the child object's metadata (override withrelationshipField/columns). A form view can now declare its child collections directly instead of composing a customobject-master-detail-formpage.Tiers, recapped
object-master-detail-formwith{ childObject }— columns/FK derived.object-formbecomes master-detail by addingsubforms.Testing
ObjectFormwithsubformsrenders the master-detail UI (md-form-submit+ child section). 77 plugin-form tests pass.@object-ui/types+@object-ui/plugin-formbuild clean — the mutualObjectForm ↔ MasterDetailFormreference is render-time only (no circular-init issue).Note: wiring object form-view metadata to populate
subformsautomatically (so the standard New/Edit screen includes children with zero page authoring) is a natural follow-up on top of this capability.🤖 Generated with Claude Code