fix: AI-built apps usable immediately — table sync on publish + valid kanban config#1559
Merged
xuyushun441-sys merged 1 commit intoJun 3, 2026
Conversation
… kanban config
Found via end-to-end testing of an AI-built app:
1) A freshly-published object couldn't take records until a restart — publish
registered it but never created its table (sync only ran at boot), so inserts
threw object_not_found. Added ObjectQL.syncObjectSchema(name) and call it from
the publish paths (publishMetaItem + saveMetaItem publish) via ensureObjectStorage.
2) AI kanban views rendered as lists / failed validation — viewBody emitted no
kanban config, but KanbanConfigSchema needs groupByField + columns. Added
blueprint view groupBy (lenient+strict) and emit list.kanban={groupByField,columns},
explicit groupBy else inferred from the object's first select field.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jun 3, 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.
Context
Found by testing a complex AI-built app (招聘管理 / ATS: 3 objects, lookups, a kanban) end-to-end as a real user. Two genuine gaps surfaced — the kind that make an AI-built app feel broken even though the metadata pipeline "succeeded".
Fixes
1. A freshly-published object couldn't accept records until a server restart
Publishing a drafted object registered it in the in-memory registry but never created its physical table — table sync (
driver.syncSchema) only ran at boot. So inserting into a just-published object failed withobject_not_found("no such table") until the next restart.ObjectQL.syncObjectSchema(objectName)— a targeted, idempotent single-object schema sync.protocol.ensureObjectStorage(type, name)calls it after the registry mutation in both publish paths (publishMetaItemandsaveMetaItemmode:'publish'). Best-effort + non-fatal.Verified live: built an app via the AI, published it, created a record with no restart — previously this threw
object_not_found.2. AI-generated kanban views rendered as lists (and could fail validation)
viewBodyemittedlist.type:'kanban'with nokanbanconfig.KanbanConfigSchemarequires bothgroupByFieldandcolumns.groupByto the blueprint view schema (lenient + strict mirror).apply_blueprintnow setslist.kanban = { groupByField, columns }— explicitgroupBywhen provided, else inferred from the object's firstselectfield.Verified live: an AI-built kanban app publishes the kanban view (4/4 artifacts) with
kanban: { groupByField: 'bug_state', columns: [...] }.Tests
New blueprint-tools kanban test; full suites green: service-ai + objectql + spec/ai = 1108 passing.
Known follow-up (objectui, out of scope)
The console still renders the kanban as a list / doesn't surface AI views as tabs — a frontend renderer gap, now unblocked because the metadata is valid.
🤖 Generated with Claude Code