feat(studio): page create form binds object + page type + kind (#1541)#1572
Merged
Conversation
The page create form only had identity fields (label/name/icon/description), so a record page couldn't be created or bound to an object in Studio — even though the edit form + protocol schema fully support type/object/kind/regions. The root cause was objectui-side: the `page` resource anchor's createFields omitted them (cf. `view`, which includes object + kind). Mirror view's create config — add Object, Page type (default 'record'), Kind (full/slotted) to the page create form. Block layout is still composed in the editor canvas. 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 7, 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 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.
Why
Verified in the browser: the Studio "New page" form was identity-only (Label / Name / Icon / Description), so you couldn't create a
pageType: 'record'page or bind it to an object — even though the page edit form and the protocol schema fully supporttype/object/kind/regions. Root cause is objectui-side, not the protocol: thepageresource anchor'screateFieldsomitted those fields (whereasviewincludesobject+kind).What
Mirror the
viewresource's create config forpage(anchors.ts):createFields+=object,type,kind.createSchemaexposing Page type (record/app/home/dashboard/utility, defaultrecord), Object (the bound object for a record page), Kind (full/slotted, defaultfull).createDefaultsseedstype: 'record', kind: 'full'.So a record page can now be created + bound to an object in Studio; the block layout is composed in the editor's PagePreview canvas (which already works).
Verification
First of the B1 (#1541) Studio-path steps. Next: seed a record page's regions from
buildDefaultPageSchema(start from the default, not blank); then the live round-trip e2e + docs.🤖 Generated with Claude Code