chore(examples): using TypeScript satisfies keyword instead of Prisma.validator

[anatolzak]

🎯 Changes

Since TypeScript introduced the satisfies keyword, it's now recommended to use it instead of Prisma.validator

From the Prisma Docs:

If you have a use case for Prisma.validator, be sure to check out this blog post about improving your Prisma 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.

https://www.prisma.io/docs/concepts/components/prisma-client/advanced-type-safety/prisma-validator

Before using Prisma.validator:

const defaultPostSelect = Prisma.validator<Prisma.PostSelect>()({
  id: true,
  title: true,
  text: true,
  createdAt: true,
  updatedAt: true,
});

After using satisfies keyword

const defaultPostSelect = {
  id: true,
  title: true,
  text: true,
  createdAt: true,
  updatedAt: true,
} satisfies Prisma.PostSelect;

✅ Checklist

• I have followed the steps listed in the Contributing guide.
• If necessary, I have added documentation related to the changes made.
• I have added or updated the tests related to the changes made.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
trpc-next-app-dir	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 22, 2023 10:47am
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 22, 2023 10:47am

[vercel]

@anatolzak is attempting to deploy a commit to the trpc Team on Vercel.

A member of the Team first needs to authorize it.

[KATT]

Feel free to search through the project and do it everywhere where we use Prisma validators :)

[anatolzak]

@KATT I fixed it everywhere else in the project in this pull request :) #5084