A Prisma error that covers all possible errors as mentioned in `Errors reference`

Problem

In any try/catch that runs a prisma query you’d have to check if the error is an instance of a specific prisma error in order to handle different kinds of errors and get the type-safety, for example if you want the the code or message property of an error.

If you want to catch all possible prisma errors you’d have to write a seperate if statement for all of them, for example if you want to log the error.

if (error instanceof Prisma.PrismaClientKnownRequestError) {
  log(error.code, error.message)
}

and so on...

If you dont do this, a possible error will not be logged because you are not checking if it’s an instance of. If you dont do any if statements you dont have the type safety

catch (error) {
  log(error.code) // type unknown, accepts a string;
  log(error.message) // type unknown, accepts a string
}

Suggested solution

A prisma error that covers all exceptions

catch (error) {
  if (error instanceof Prisma.Error) {
    log(error.code, error.message) // this will log any error that prisma throws + typesafety. both code and message are a string
  } 
}

Alternatives

Additional context

[Prince-Rabadiya]

Would love a better way to handle errors. Even a property on the error object that returns just the error itself would be fantastic. I really don’t want to return:

Invalid `prisma.user.update()` invocation in
/home/leonardo/ironeko-fondamenta/.next/server/pages/api.js:127:32

  124   prisma
  125 }) => {
  126   try {
→ 127     return await prisma.user.update(
  An operation failed because it depends on one or more records that were required but not found. Record to update not found. 

To my frontend.

can specify it like this

new PrismaClient({
    errorFormat: 'minimal',
  })

refer this for more info

[system32uwu]

Crazy that you can get this highly detailed error message from the engine

  20 async create(data: CreateUserDto) {
→ 21   const user = await this.prismaService.user.create({
         data: {
           email: '[e-mail]',
           password: '$2a$10$CBE/dMtwekhH9IlocK1cPOXr9g.NfI3pCmaSmLFVOYv5yvkbBdY26',
       +   name: String,
       +   surname: String,
       ?   walletAddress?: String | null,
       ?   role?: INVESTOR | AGENT
         }
       })

Argument name for data.name is missing.
Argument surname for data.surname is missing.

Note: Lines with + are required, lines with ? are optional.

But not this from the client to just deliver it in the response:

{
  code: 123,
  meta: ['name', 'surname'],
  message: 'missing required fields'
}

Of course you can still use schema validators, but then what’s the point of using an ORM at all? You’re going to be re-defining your schema just to get the validation working