Prisma

image.png

Is it possible to distinguish in the `rejectOnNotFound` to which of the provided where conditions makes the query return `null`? (see screenshot with code)

Otherwise, I’d have to run some queries for the provided ids, e.g.
1. check first where condition (authorId)
```const post = await ctx.prisma.post.findFirst({
  where: { authorId },
  rejectOnNotFound: (e) =&gt; Error(`Unable to find a post for author with id ${authorId}`),
});```
2. check second where condition (departmendId) similarly
3. If both don’t throw, I return my actually query with both `where`s

I know you guys have an epic open about Error Management, but I was unable to find anything for this particular use case (which I encounter quite often!)
<https://github.com/prisma/prisma/issues/3488>

Hey Richard :wave:,

This is not possible today, but sounds like a great feature request to capture. Would you mind <https://github.com/prisma/prisma/issues/new?assignees=&amp;labels=&amp;template=feature_request.md&amp;title=|filling one out>?

Hi <@U02HXQHCTR8> thanks for the quick turnaround. I’ve filed <https://github.com/prisma/prisma/issues/13316|an issue> about this.