Service Classes (e.g. for NestJS)

Problem

Dear Prisma Team, for my upcoming project, i would like to use Prisma, since it is ready to be used in production. I have been around for a year or so, but now finally use it in a concrete project. I really like what you've been working on - Prisma looks great and i can't wait to try it out. Problem In the context of my project i will be building a RESTful API with `NestJS`. Unfortunately, because of various reasons I cannot rely on GraphQL, for example, existing 3rd party clients are not able to "speak" (i.e., work with) GraphQL. In order to reduce boilerplate code in my `Service`s, i thought it may be a good idea to create some kind of _generic_ `CrudService` that offers basic functionality, like `create`, `update`, ... as some kind of wrapper around `prisma`. Having used `typeorm` in projects before, i thought that this may be an easy task. However, i quickly hit some roadblocks, because there are no `Repositories` in Prisma like in typeorm. The next idea was to simply _inject_ (i.e., pass) the corresponding `Delegate` to the `CrudService`. The closest i could get, however, is like this: [code block] and then create a concrete `UserService` like this: [code block] While this works, it has a few drawbacks: 1. all `modelDelegate` methods (i.e, `create()`, `update()`, `findMany()`, ...) are unknown, because the `delegate` is not known 2. the `UserService` with all its generics looks very ugly Suggested solution Regarding the drawbacks discussed earlier, i would sug