From 30a5d8c03f95e1a19be7f293c07012db7bd8d062 Mon Sep 17 00:00:00 2001 From: Arthur Gamby Date: Fri, 17 Oct 2025 14:52:51 +0200 Subject: [PATCH] docs: update Prisma.validator api availability information in client versions --- .../200-prisma-client/400-type-safety/050-prisma-validator.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx b/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx index 47afa0a179..59aab3fdc5 100644 --- a/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx +++ b/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx @@ -12,7 +12,8 @@ This page introduces the `Prisma.validator` and offers some motivations behind w -> **Note**: If you have a use case for `Prisma.validator`, be sure to check out this [blog post](https://www.prisma.io/blog/satisfies-operator-ur8ys8ccq7zb) about improving your Prisma Client workflows with the new TypeScript `satisfies` keyword. It's likely that you can solve your use case natively using `satisfies` instead of using `Prisma.validator`. +> **Note**: If you have a use case for `Prisma.validator`, be sure to check out this [blog post](https://www.prisma.io/blog/satisfies-operator-ur8ys8ccq7zb) about improving your Prisma Client workflows with the new TypeScript `satisfies` keyword. +> This API only exists when using the old `prisma-client-js` generator, and is not available in `prisma-client`. It's likely that you can solve your use case natively using `satisfies` instead of using `Prisma.validator`. ## Creating a typed query statement