Setting rejectOnNotFound globally doesn't provide type safety

Bug description

Setting rejectOnNotFound globally doesn’t change the typing of findUnique or findFirst

const prisma = new PrismaClient({
  rejectOnNotFound: true,
});

Then when I use findUnique, It still returns Prisma.Prisma__UserClient<User | null> instead of Prisma.Prisma__UserClient<User>

Expected behavior

It will be better if it’s typed. This might mean, generating types at runtime just like nexus does. But a better approach will be to just include this property rejectOnNotFound in the prisma schema itself within the generator block like this:

generator client {
  provider = "prisma-client-js"
  rejectOnNotFound = true
}

Environment & setup

• OS: Windows
• Database: PostgreSQL
• Node.js version: 14.16.1
• Prisma version:

 2.21.2

[pantharshit00]

@ahmedosama7450 I don’t think we can have this option in the schema as people can do multiple instances of the client with different rejectOnNotFound option (eg. when sharing client in a monorepo) and the schema approach restricts that.

I opened a documentation issue about the generic usage: https://github.com/prisma/docs/issues/1564#issuecomment-883668535

[pantharshit00]

@toy-crane You need to do the following:

import { PrismaClient } from "@prisma/client";

export const createPrismaClient = (): PrismaClient<{
  rejectOnNotFound: true;
}> => {
  const prisma = new PrismaClient({
    rejectOnNotFound: true,
  });
  return prisma;
};