Rename User relation to author in Post model

[martinmona]

Summary by CodeRabbit

• Documentation
  • Renamed the Post relation field from "user" to "author" (and the corresponding id) in schema examples for clearer, more consistent naming.
  • No change to relation behavior or constraints—only public field names were updated for clarity.

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

[coderabbitai]

Walkthrough

Updated a Prisma schema example: in the Post model the relation and foreign-key field were renamed from userId/user to authorId/author, preserving @relation attributes (fields, references, onDelete, onUpdate) and behavior.

Changes

Cohort / File(s)	Summary
Prisma Schema Documentation content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx	Renamed Post model relation field and FK: user → author, userId Int? → authorId Int?. Relation attributes updated to @relation(fields: [authorId], references: [id], onDelete: SetNull, onUpdate: Cascade); semantics unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix(prisma-schema): improve documentation readability #7363: Also edits Post model relation/field naming in Prisma schema docs (renames/adjusts author/user field declarations).

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 pull request title directly and accurately describes the main change: renaming the User relation field to author in the Post model, which matches the file modifications shown in the summary.
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 8010f52 and d59dc36.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx

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

• content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx

---

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: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx (1)

116-116: Update field name reference in documentation text.

The explanatory text references userId, but the field has been renamed to authorId in the code example above.

🔎 Proposed fix

-- If you delete a `Tag`, the corresponding tag assignment is also deleted in `TagOnPosts`, using the `Cascade` referential action
-- If you delete a `User`, the author is removed from all posts by setting the field value to `Null`, because of the `SetNull` referential action. To allow this, `User` and `userId` must be optional fields in `Post`.
+- If you delete a `User`, the author is removed from all posts by setting the field value to `Null`, because of the `SetNull` referential action. To allow this, `User` and `authorId` must be optional fields in `Post`.

📜 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 2bcc421 and 8010f52.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx