feat(spec): interface-editor polish — composite disclosure popover + buttons=object-actions#2051
Merged
Merged
Conversation
Adds `disclosure?: 'inline' | 'popover'` to FormFieldSchema. A composite field marked `disclosure: 'popover'` renders as a compact summary line + a gear that opens its sub-fields in a popover (Airtable-style progressive disclosure), instead of an always-expanded inline box — keeping the interface-page panel lean. Applied to the page form's `appearance`, `userActions`, and `addRecord` composites (the dense sub-toggle groups). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…icker) `InterfacePageConfig.buttons` is now a first-class field: an array of the source object's action names (ActionSchema) surfaced as page toolbar buttons. The page form renders it with the new `action-multi` widget (dependsOn: source), so the author picks from the object's real actions — buttons ARE object actions, correct-by-construction (no free-text IDs). - page.zod.ts — add `buttons: z.array(z.string())` to InterfacePageConfigSchema. - page.form.ts — add the Buttons field (widget: action-multi) under User actions. - showcase task-workbench demonstrates it: buttons: ['showcase_bulk_reassign', 'showcase_mark_done'] render as Reassign… / Mark Done in the page header. Pairs with the objectui action-multi widget + InterfaceListPage runtime render. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📓 Docs Drift CheckThis PR changes 1 package(s): 89 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
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
1 participant
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
Spec side of the interface-page editor polish (pairs with the objectui runtime PR).
Progressive-disclosure popover
FormFieldSchemagainsdisclosure?: 'inline' | 'popover'. A composite markeddisclosure: 'popover'renders as a summary line + gear popover instead of an inline box.appearance/userActions/addRecordwithdisclosure: 'popover'.Buttons = object actions
InterfacePageConfigSchemagainsbuttons: z.array(z.string())— names of the source object's actions surfaced as page toolbar buttons.action-multiwidget (dependsOn: source) so the author picks from the object's real actions (correct-by-construction).task-workbenchdemonstrates it:buttons: ['showcase_bulk_reassign', 'showcase_mark_done']→ Reassign… / Mark Done in the page header.Verification
Browser-tested against the live showcase (see objectui PR): the Buttons picker lists the task object's actions, the workbench header renders them, and the composite popovers collapse/expand correctly. Spec
tscclean.🤖 Generated with Claude Code