fix(ai): AI-authored views bind to their object + render (kanban as a board, not a list)#1563
Merged
Merged
Conversation
… board)
AI-built app views (incl. kanban) only showed as the default list, never as
tabs. Root cause was the blueprint viewBody emitting a bare { list: {…} }
fragment instead of the canonical view record. Missing: top-level `name`
(getMetaItems only surfaces overlay rows whose body has name → AI views were
dropped from the object's view list), top-level `object`/`viewKind` (console
binds views to objects via these), and the `<object>.<key>` name prefix.
viewBody now emits { name:'<obj>.<key>', object, viewKind:'list'|'form', config }
matching the showcase's own views (validated vs the real ViewSchema). E2E
verified: AI kanban app surfaces view tabs + renders the board grouped by status.
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.
Problem
An AI-built app's views — including a "kanban by status" — never appeared as selectable view tabs and always rendered as the default list. The user pointed out the showcase's own kanban renders fine, which ruled out the renderer.
Diagnosis: metadata-shape bug in the blueprint's
viewBody(not renderer, not skill)Comparing the AI view to the working showcase view (
showcase_project.by_status):nameshowcase_project.by_statusobjectshowcase_projectviewKindlistconfiglistviewBodyemitted a bare{ list: {…} }fragment. Three concrete failures:name→protocol.getMetaItemsonly merges sys_metadata overlay rows whose body hasname(protocol.ts ~L1188'name' in data). Every AI view (always an overlay) was silently dropped fromgetMetaItems({type:'view'})→ the object page's view list was empty → no tabs.object/viewKind→ the console can't bind the view to its object.<object>.<key>-prefixed → the convention the console keys an object's view tabs off.Fix
viewBodynow emits the canonical view record (matching the showcase's own views):Validated against the real
ViewSchema(getMetadataTypeSchema('view')).Verification (end-to-end, browser)
Built a fresh AI app with a "kanban by stage" view → published → opened the object page:
getMetaItems({type:'view'})now listsfeature_req.feature_req_kanban+feature_req.feature_req_list(was empty).service-ai blueprint suite green (25).
🤖 Generated with Claude Code