feat(spec): inlineEdit on relationship fields — declarative master-detail#1615
Merged
Conversation
Field.inlineEdit (+ inlineTitle/inlineColumns/inlineAmountField) on master_detail/lookup fields declares "edit these children inline within the parent form" — the parent's standard form then auto-renders an atomic master-detail form (objectui derives the UI). showcase: showcase_task.project sets inlineEdit so New/Edit Project auto-shows a Tasks subtable; the project view's explicit subforms are dropped (now derived). spec field tests 6647 pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
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
2 participants
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
Lets a relationship declare master-detail inline editing in the data model, so the parent's standard form auto-renders it — answering "why not define inline editing at the object/relationship level instead of per-form?"
A
master_detail/lookupfield can setinlineEdit: true(+ optionalinlineTitle/inlineColumns/inlineAmountField):→ every standard New/Edit Project form renders an atomic master-detail (project fields + inline Tasks grid). No form view config, no bespoke page. The objectui metadata layer derives the
subformsfrom this (PR pairs with objectui).master_detailchildren withoutinlineEditare NOT inlined → associations (comments/attachments) stay out of the entry form.form.subformsoverrides the derived one.Showcase:
showcase_task.projectsetsinlineEdit; the project view's explicitsubformsis removed (now derived from the relationship).Spec field suite: 6647 pass. Live-verified end-to-end via objectui's e2e.
🤖 Generated with Claude Code