Olivier

Hi there, this was a problem for our team also as our existing code uses Loopback operation hooks (on save, on delete etc). In order to move over to Prisma...

> Big thanks for sharing, @olivierwilkinson - this is fantastic. No problem, I'm glad you are finding it useful 😄 > Minor observation that it seems to work with Prisma...

> Could this be released as a standalone npm package while we wait for the core team to adopt something similar (or better) ? I can do that for the...

@lewebsimple @andyjy I've published an npm package [prisma-nested-middleware](https://github.com/olivierwilkinson/prisma-nested-middleware) with the code I posted above. 👍

Heya, I've continued working on the [prisma-nested-middleware ](https://github.com/olivierwilkinson/prisma-nested-middleware) package that I mentioned above. It now calls the middleware function for relations found in include, select and where objects, and can...

Just so everyone is aware, since middleware has been deprecated I've ported the work I did for the [prisma-nested-middleware](https://github.com/olivierwilkinson/prisma-nested-middleware) package to work for extensions, you can find it at [prisma-extension-nested-operations](https://github.com/olivierwilkinson/prisma-extension-nested-operations)....

Heya, Sorry for the slow response, I'm planning on looking into this soon! Hopefully I'll have a solution this week, but it may take longer as supporting multiple versions of...

Hi there 👋 Thanks for raising this. I wasn't able to reproduce the issue, but I did have to change the example to `await` the selector call before calling `waitForDisplayed`:...

Hi again, sorry for the slow response! I've been on holiday 😄 Thanks for the extra information, I've aligned our package versions but unfortunately I'm still unable to reproduce the...

> Another thing I notice is that when the element can't actually be found, I do get an error thrown that this is the case. When I use a selector...