Repository navigation
fix(init): keep an existing schema when offering the demo - #617
Merged
Brooooooklyn merged 1 commit intoOct 27, 2026
Merged
Conversation
Member
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://fix-init-keep-existing-schema-void-cloud.voidzero-docs.workers.dev (commit 05c98a8)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Brooooooklyn
force-pushed
the
fix/init-keep-existing-schema
branch
from
October 27, 2026 07:54
1d05eeb to
efe4402
Compare
In an existing project that had only a hand-written db/schema.ts, answering yes to "Scaffold demo code?" in `void init` replaced that schema with the demo posts table. src/demo.ts was overwritten the same way. Init now skips the demo, before asking, when the project already has a Drizzle schema or when any demo file (db/schema.ts, routes/api/posts.ts, src/demo.ts) already exists, and logs why. The demo is written whole or not at all. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brooooooklyn
force-pushed
the
fix/init-keep-existing-schema
branch
from
October 27, 2026 08:06
efe4402 to
05c98a8
Compare
Brooooooklyn
enabled stacked auto-merge (squash)
October 27, 2026 08:34
Brooooooklyn
disabled stacked auto-merge
October 27, 2026 08:34
fengmk2
approved these changes
Oct 27, 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.
Problem
In an existing project that has only a hand-written
db/schema.ts,void initstill offers "Scaffold demo code?". Saying yes replaces the schema with the demopoststable.src/demo.tsis overwritten the same way.What changed
demoFiles(root)returns the three demo targets.scaffoldDemo()now writes to those paths.Tests
db/schema.tsstays byte-identical, the demo is skipped with the message, and no other demo file is written.src/demo.tsstays unchanged and no half demo is written.Choices to check
🤖 Generated with Claude Code