Update Prisma schema path in overview document

[luzede]

Changes schema path in the example to match a directory instead of a file. For multi file prisma schemas a directory needs to be provided that will have schema.prisma inside.

Summary by CodeRabbit

• Documentation
  • Updated schema configuration examples to demonstrate directory path usage for flexible schema organization.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A single documentation file was updated to modify a configuration example. The Prisma schema path in a multi-file schema usage snippet was changed from pointing to a specific file (prisma/schema.prisma) to pointing to a directory (prisma/), reflecting a directory-based schema location approach.

Changes

Cohort / File(s)	Change Summary
Documentation example update content/200-orm/100-prisma-schema/10-overview/04-location.mdx	Updated the multi-file Prisma schema configuration example, changing the schema field from 'prisma/schema.prisma' to 'prisma/' to reflect directory-based schema location specification

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is a straightforward documentation example update affecting a single file. The change is minimal, localized, and cosmetic in nature—simply correcting the configuration path in an example snippet without introducing logic changes or new concepts.

Possibly related PRs

• fix: clarify schema.prisma file location better DC-6209 #7261: Modifies the same documentation file to update schema location examples and guidance from single-file to directory-based configuration
• fix: add callout to Prisma Config DC-4961 #7095: Edits the same documentation file and addresses Prisma schema location specification with PrismaConfig examples

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: updating a Prisma schema path in documentation. It directly reflects the file modification shown in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

content/200-orm/100-prisma-schema/10-overview/04-location.mdx (1)

72-72: Minor: Standardize path format across examples for consistency.

The three examples use slightly different path formats for directory locations:

• Line 72: ./prisma (dot-slash prefix)
• Line 78: ./prisma (dot-slash prefix)
• Line 88: prisma/ (no dot-slash, trailing slash)

All are valid, but standardizing the format would improve clarity. Consider updating line 88 to ./prisma to match lines 72 and 78.

  export default defineConfig({
-   schema: 'prisma/',
+   schema: './prisma',

Also applies to: 78-78, 88-88

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2485d01 and 8cc6c7d.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/10-overview/04-location.mdx (1 hunks)

🔇 Additional comments (1)

content/200-orm/100-prisma-schema/10-overview/04-location.mdx (1)

88-88: ✓ Correctly updates schema path to directory format.

The change aligns the prisma.config.ts example with the documented requirement (line 68) that multi-file Prisma schemas must use a directory path. This is now consistent with the package.json example on line 78, and the warning section (line 107) properly reinforces this expectation.

[AmanVarshney01]

Thanks for the PR @luzede ❤️