improve: port middleware to extension

[ruheni]

This PR migrates the package from Prisma middleware to Prisma Client extensions because middleware was deprecated in v4.16.0.

Would we separate prisma-redis-middleware into two packages: a middleware & a client extension, or migrate the middleware to Prisma Client extensions? The latter would be a breaking change, and the former would be a safe alternative for those who would still like to use it as middleware.

Happy to hear your thoughts and make any necessary changes.

Most of the code was reusable from the middleware with a few minor tweaks such as argument names.

TODO:

• Add tests

Closes #546

[phiko-misc]

Is there any update on this?

[ruheni]

@Asjas, I would appreciate your input on the way forward for changes. :)

[net-tech]

@ruheni Are tests the only thing missing or is the implementation not finished? Looking into whether I should fork your fork so I can get access to this sooner if the author doesn't reply soon.

[Asjas]

Would we separate prisma-redis-middleware into two packages: a middleware & a client extension, or migrate the middleware to Prisma Client extensions?

Whichever is the easiest, I don't make heavy use of this library anymore so whichever one you want to implement I don't see an issue with 🙁

[phiko-misc]

Some news? @ruheni

[ruheni]

👋

Picking this up this week. I'll convert the repo to a monorepo containing the extension and middleware. Will keep you posted and share more updates!

Apologies for the delayed updates.