add docs for 6.14.0

[nikolasburk]

Summary by CodeRabbit

• Documentation
  • Improved clarity and accuracy of the Prisma ORM views documentation.
  • Updated and expanded explanations of restrictions on views, including primary keys, indexes, and uniqueness constraints.
  • Clarified Prisma Client API limitations for views.
  • Enhanced step-by-step instructions and reworded notes for better readability.

[coderabbitai]

Walkthrough

The documentation for Prisma ORM's views preview feature was updated to improve clarity and accuracy. The explanation of restrictions on views was restructured and expanded, clarifying the rationale behind limitations on identifiers, indexes, and uniqueness constraints. Prisma Client API support details were refined, and procedural steps and notes were reworded for smoother phrasing.

Changes

Cohort / File(s)	Change Summary
Prisma Views Documentation content/200-orm/100-prisma-schema/20-data-model/40-views.mdx	Clarified and restructured documentation for Prisma views, converting steps to a numbered list, simplifying notes on unsupported operations, expanding restrictions on @id, indexes, and @unique, and refining Prisma Client API limitations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d971a75 and 95620a8.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/20-data-model/40-views.mdx (5 hunks)

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

• content/200-orm/100-prisma-schema/20-data-model/40-views.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). (3)

• GitHub Check: Check internal links
• GitHub Check: runner / linkspector
• GitHub Check: Lost Pixel

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/6.14.0

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[github-actions]

original	preview
content/200-orm/100-prisma-schema/20-data-model/40-views.mdx	content/200-orm/100-prisma-schema/20-data-model/40-views.mdx

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

content/200-orm/100-prisma-schema/20-data-model/40-views.mdx (2)

15-18: Consider explicit list numbering for raw-file readability

Using “1.” for every item renders correctly in Markdown, but it makes the raw source harder to scan and creates noisy diffs when items are reordered.
Switching to 1., 2., 3., 4. (or letting the formatter handle it) would improve maintainability without affecting the rendered output.

---

39-39: Re-phrase to avoid repetitive wording

“…preview feature in our dedicated preview feature feedback issue…” repeats “preview feature” twice. A concise alternative:

Please leave feedback in the dedicated views preview feature issue

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23d8d87 and d6b1bb3.

📒 Files selected for processing (1)

• content/200-orm/100-prisma-schema/20-data-model/40-views.mdx (4 hunks)

🧰 Additional context used

🪛 GitHub Actions: Documentation Checks

content/200-orm/100-prisma-schema/20-data-model/40-views.mdx

[error] 336-336: cspell: Unknown word 'contraints'. Suggested fix: 'constraints'.

---

[error] 338-338: cspell: Unknown word 'attributre'.

⏰ 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). (3)

• GitHub Check: Check internal links
• GitHub Check: runner / linkspector
• GitHub Check: Lost Pixel

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	95620a8
Status:	✅  Deploy successful!
Preview URL:	https://eb558c13.docs-51g.pages.dev
Branch Preview URL:	https://docs-6-14-0.docs-51g.pages.dev

View logs