Skip to content

Conversation

ArthurGamby
Copy link
Contributor

@ArthurGamby ArthurGamby commented Oct 17, 2025

Summary

This PR clarifies that the prisma.validator API is only available when using the legacy prisma-client-js generator, and not in the new prisma-client.

Visual Changes

Before After
Screenshot 2025-10-17 at 14 18 42 Screenshot 2025-10-17 at 16 45 27

Preview link

https://feat-dc-5685-prisma-validato.docs-51g.pages.dev/orm/prisma-client/type-safety/prisma-validator

Related Issue

Linear issue → DC-5685

Copy link
Contributor

Dangerous URL check

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

Copy link
Contributor

coderabbitai bot commented Oct 17, 2025

Walkthrough

Replaced an inline Note with a Warning in the Prisma Validator docs clarifying that Prisma.validator is only available with the legacy prisma-client-js generator, not the new prisma-client, and retained guidance linking to TypeScript's satisfies usage.

Changes

Cohort / File(s) Summary
Documentation clarification
content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx
Replaced inline Note with a Warning stating Prisma.validator is only available with the legacy prisma-client-js generator (not prisma-client), and preserved link/guidance about TypeScript's satisfies.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

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 "DC 5685 - update Prisma.validator api availability information in client versions" directly and accurately describes the main change in the changeset. The title clearly conveys that the PR updates information about the Prisma.validator API's availability across different client versions, which aligns with the actual changes: replacing inline documentation with a warning that clarifies the API is only available in the legacy prisma-client-js generator and not in the new prisma-client. The title is specific and non-generic, avoiding vague terms, and a teammate scanning the repository history would immediately understand the primary purpose of this change.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

📜 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 2ecd2bb and 8e32795.

📒 Files selected for processing (1)
  • content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx (1 hunks)
⏰ 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). (2)
  • GitHub Check: Check internal links
  • GitHub Check: runner / linkspector
🔇 Additional comments (3)
content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx (3)

15-21: Excellent clarity and guidance for deprecated API.

The warning block effectively communicates that Prisma.validator is legacy, provides a clear technical reason (only with prisma-client-js generator), and helpfully guides users toward the modern alternative (satisfies operator). The progression from limitation → alternative → learning resource is pedagogically sound and provides a smooth migration path for users.


15-16: No issues found—terminology is consistent and accurate.

The warning correctly uses official Prisma terminology. Web search of Prisma documentation confirms that prisma-client-js is the legacy generator and prisma-client is the new generator. The codebase reinforces this: AI guidance explicitly directs developers to use provider = "prisma-client" rather than the legacy option. The terminology in lines 15-16 is consistent with both official Prisma documentation and existing documentation references throughout the repository.


15-21: No issues found. Warning block is accurate and well-supported.

The verification confirms all claims in the warning block are factually correct:

  • Prisma.validator is only available in the legacy prisma-client-js generator and not in the new prisma-client generator
  • TypeScript's satisfies operator (available in TS 4.9+) provides zero runtime cost while delivering equivalent or better type checking compared to Prisma.validator
  • The external blog post link is valid (HTTP 200)
  • The recommendation is consistent with other documentation pages that reference satisfies as the replacement
  • Formatting and indentation are correct

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

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

Copy link
Contributor

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.

Copy link

cloudflare-workers-and-pages bot commented Oct 17, 2025

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0fb1973
Status: ✅  Deploy successful!
Preview URL: https://55acf1e5.docs-51g.pages.dev
Branch Preview URL: https://feat-dc-5685-prisma-validato.docs-51g.pages.dev

View logs

Copy link
Contributor

coderabbitai[bot]
coderabbitai bot previously approved these changes Oct 17, 2025
@ArthurGamby ArthurGamby force-pushed the feat/DC-5685-prisma-validator-api-availability-in-client-versions branch from 2ecd2bb to 8e32795 Compare October 17, 2025 14:43
@ArthurGamby ArthurGamby merged commit c83fa74 into main Oct 21, 2025
8 checks passed
@ArthurGamby ArthurGamby deleted the feat/DC-5685-prisma-validator-api-availability-in-client-versions branch October 21, 2025 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants