feat(spec): FormViewSchema.subforms for config-driven master-detail#1613
Merged
Conversation
A form view can declare inline child collections (subforms), letting an
object's standard create/edit form render as an atomic master-detail form
with no bespoke page. Each entry needs only { childObject } (FK + columns
derived from the child object metadata). Additive/optional; spec suite
6647 pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Adds an optional
subformsarray toFormViewSchemaso a form view can declare inline child collections. This lets an object's standard create/edit form render as an atomic master-detail form (object fields + child grids) with no bespoke page. Each entry needs onlychildObject— the relationship FK and grid columns are derived from the child object metadata (override viarelationshipField/columns).Additive/optional; the spec suite passes (6647). Pairs with objectui:
ObjectFormalready renderssubforms, andObjectViewforwardsform.subforms.🤖 Generated with Claude Code