Enable Workspace creation in the demo - #762
Draft
luokerenx4 wants to merge 1 commit into
Draft
Conversation
|
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.
Summary
Root cause
The Demo POST
/api/workspacesroute returned a nested{ error: { ... } }object even though the client expects the production{ error, message }shape. The form stored that object as renderable error text, causing React to crash to a blank page. The route also disabled a prominent mutation despite the Demo banner promising non-persistent mutations.Verification
pnpm vitest run ui/src/demo/handlers/workspaces-create.spec.tsnpx tsc --noEmitcd ui && npx tsc -bpnpm test(358 passed, 1 skipped; 3391 tests passed, 9 skipped)git diff --checkchat-jul29, navigated to/workspaces/demo-created-ws-1, confirmed the empty Workspace/session surface renders, then retried the same tag and confirmed an inline duplicate error without a crashBoundary touch