fix(prisma-schema): improve documentation readability

[Hephaest]

Hi team,

I have reviewed the entire Prisma Schema section today, and I have identified a few areas that could be improved.

For more details, please check out my inline comments :)

Summary by CodeRabbit

• Documentation
  • Updated schema examples: Post and Comment relations and their foreign keys are now shown as required (non-optional) in both relational and MongoDB examples for clearer, consistent modeling.
  • Minor formatting tweaks: adjusted comment placement in index documentation examples.

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

[coderabbitai]

Walkthrough

This PR updates Prisma schema examples in the docs to make several relation fields required (non-optional) and adjusts corresponding foreign key scalar nullability; it also repositions two comment lines within index documentation blocks.

Changes

Cohort / File(s)	Summary
Overview schema updates content/200-orm/100-prisma-schema/10-overview/index.mdx	In relational and MongoDB examples, Post.author changed from User? → User; relational authorId changed from Int? → Int. MongoDB authorId (String @db.ObjectId``) remains typed but the relation is now required.
Data-model updates content/200-orm/100-prisma-schema/20-data-model/10-models.mdx	In relational and MongoDB examples, Comment.post changed from Post? → Post; postId changed from Int? → Int (relational) and from String? → String (MongoDB). Minor formatting tweaks to MongoDB id field noted.
Index documentation formatting content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx	Two comment lines describing operator class and index type were moved from before to after their corresponding @@index directives; no semantic changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title 'improve documentation readability' is vague and doesn't reflect the substantive schema changes: making author/post relations required instead of optional across relational and MongoDB models.	Revise the title to specifically indicate the schema changes, such as 'Make author and post relations required in schema documentation' or similar, to accurately communicate the primary modification.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent 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 022194b and 2b5ecae.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Check internal links

---

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.}

[AmanVarshney01]

Makes sense! Thanks for the PR @Hephaest ❤️