No way to catch error in findUniqueOrThrow via middleware

[janpio]

Also their is no way to catch and massage the error (to change its message for example).

With findUniqueOrThrow, in a middleware result is null and params.action is findUnique:

prismaClient.$use(async (params, next) => {
  try {
    const result = await next(params);
    return result;
  } catch (error) {
    // nothing to see here
    throw error;
  }
});

With rejectOnNotFound, the un-exported error (treatable with error.constructor.name === 'NotFoundError' btw) was thrown inside.

Originally posted by @bbenezech in #14209 (comment)

[janpio]

@bbenezech this sounds like a separate issue for me, is that right? If that's the case, could you please open a separate GitHub issue for this to avoid any confusion, and, most importantly, avoid your report being lost, since the issue @PatrikValkovic refers to has already been fixed, and someone might close it without looking at your comment.

Originally posted by @aqrln in #14209 (comment)

[miguelff]

Tracked in #16226