docs: show the config file that prisma init actually writes on the v7 quickstarts - #8301
ankur-arch wants to merge 3 commits into
Conversation
… quickstarts
The Prisma ORM 7 quickstart and add-to-existing-project pages said
`prisma init` creates `prisma.config.ts` with `env("DATABASE_URL")` from
`prisma/config`. Running `npx prisma@prev init` (prisma 7.10.0) in a
clean directory writes `prisma7.config.ts` with the generator comment,
no `env` import, and `url: process.env["DATABASE_URL"]`. Prisma 7.9
still wrote `prisma.config.ts`.
The fifteen pages pinned to `prisma@prev` now show the file as generated
and carry a note about the rename. The two MongoDB pages are pinned to
prisma 6.19.3 and are left as they are.
Closes #7818
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (16)
Included review availability: 2 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. WalkthroughThe documentation now reflects ChangesPrisma configuration documentation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other · Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to The documentation changes consistently update Prisma 7 configuration examples and the Studio config path; no concrete merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🍈 Lychee Link Check Report229 links: ✅ All links are working!Full Statistics Table
|
… too The page is pinned to prisma@prev like the other fifteen v7 quickstart pages but still showed prisma init writing prisma.config.ts with env(), and its Studio command passed --config ./prisma.config.ts, a file init no longer writes. Now shows the generated prisma7.config.ts, the rename note, and points --config at it.
|
Reviewed 99ffc68 and pushed one fix. Verified
Found and fixed
Not this PR's to fix (will propose as a follow-up task): Re-reviewing the new head cold in a couple of minutes. — reviewer |
|
Review clean at 31ffd06 What it does. On the sixteen v7 getting-started pages that install Verified on this head, from scratch
Risk: low. Prose and code samples only, on pages whose command output I reproduced; no code, redirects, or nav touched. Follow-up proposed as a separate task (not this PR's scope): five other pages that install — reviewer |
Fixes #7818.
The Prisma ORM 7 quickstart and add-to-existing-project pages said
prisma initcreatesprisma.config.tswithenv("DATABASE_URL")imported fromprisma/config. Runningnpx prisma@prev init(prisma 7.10.0) in a clean directory writesprisma7.config.tswith the generator comment, noenvimport, andurl: process.env["DATABASE_URL"]. Prisma 7.9 still wroteprisma.config.ts.The fifteen pages pinned to
prisma@prevnow show the file as generated, rename it in the bullet and the code block title, and carry a short note about the rename and that the Prisma 7 CLI discovers either name. The two MongoDB pages are pinned to prisma 6.19.3 and are left alone.Validation
npx -y prisma@prev init --datasource-provider postgresql --output ../generated/prismain an empty directory: writesprisma7.config.tswith the content now shown; the CLI's next-steps text says "Configure your DATABASE_URL in prisma7.config.ts".npx -y prisma@7.9 init ...: writesprisma.config.ts.check-ai-signs.shclean on all fifteen pages.🤖 Generated with Claude Code
Summary by CodeRabbit
prisma7.config.ts.DATABASE_URLdirectly from environment variables.