Uh oh!
There was an error while loading. Please reload this page.
feat(spec): ADR-0047 — interface/list pages get a lean, relevant config form - #1817
Merged
Merged
Conversation
… section prominent Page form (page.form.ts) reorg so interface/list pages get a lean, relevant panel instead of the generic page-form dump: • Data Context + Layout sections gain visibleOn data.type != 'list' (region designer / page object don't apply to a list surface) • Interface section: collapsed:false (primary content), name for i18n • interfaceConfig sub-fields reordered (common first, rare last); source gets the ref:object picker; sourceView/userActions/etc. helpText • type field helpText notes 'list' = interface page Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jun 14, 2026
os-zhuang added a commit
that referenced
this pull request
Jun 20, 2026
…2072) The landing KPIs all rendered with the neutral grey icon (object-metric's default colorVariant) and an empty card bottom, which read flat. Opt them into the metric palette and add a one-line sublabel so the tiles are colorful and informative: • Home — Projects (blue), Tasks (purple), Accounts (teal), Open Tasks (amber) • My Work — Open Tasks (blue), In Review (amber), At-Risk (rose) Each gains a description (active & planned / not done / awaiting review / …) that fills the previously-empty space. Pairs with objectui #1817 (tabular-nums on the metric value). Browser-verified on :5181. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
Why
On an interface/list page, the page editor showed the full generic page form — page type/template, Data Context (object/variables), and the region designer (Layout) — none of which apply to a curated list surface. The interface config was buried at the bottom with raw inputs.
This reorganises
page.form.ts(the form layout served via/meta) so a list page gets only the relevant, well-ordered controls. Pairs with the objectui renderer PR (collapsible sections + multi-select widget).Changes (
packages/spec/src/ui/page.form.ts)visibleOn: "data.type != 'list'"— hidden for list/interface pages (the region designer and page-level object don't apply).collapsed: false(primary content for a list page, still collapsible),namefor i18n.interfaceConfigsub-fields reordered — common authoring controls first (source, sourceView, appearance, userFilters, userActions, addRecord, showRecordCount), rarely-used last (filterBy, levels, allowPrinting);sourcegets theref:objectpicker; added helpText throughout.typefield helpText notes thatlist= interface page.Form-definition only — no schema/runtime change. Requires
pnpm --filter @objectstack/spec build.Verification
Built the spec dist and served it from a local showcase backend; confirmed via
/api/v1/metathat the page form now carries thevisibleOn/collapsed/ordering above. The objectui renderer (companion PR) honours these flags — covered by component tests there.🤖 Generated with Claude Code