Ondřej Švanda

I've used the [`Joi`](https://joi.dev/) schema validator before, which has this exact feature - treating your TS types as the source of truth: ```ts import * as Joi from 'joi' interface...

I have done a similar thing as OP with [openapi-generator](https://github.com/OpenAPITools/openapi-generator). Orval seems much more lightweight, but sadly the lack of this feature is a deal breaker for truly type-safe APIs.

I think the easiest way to solve this would be to create a new configuration option - something like `customTypeMapping`, which would take a map of _openapi type_ to _typescript...

Hey, thanks for the offer. I don't think I want a very rigid structure of the issue format as it often discourages people (me included) from opening it in the...

As far as I know, there is only one plugin entry point, which is the `onReleaseAvailable`. Is a diagram really needed?

If you use NestJS, please have a look at the [`@nestjs-cls/transactional`](https://papooch.github.io/nestjs-cls/plugins/available-plugins/transactional) plugin for `nestjs-cls`, which uses AsyncLocalStorage to propagate the transaction. See also https://github.com/prisma/prisma/issues/5729#issuecomment-1904507525

> No need for this much of tooling I wholeheartedly agree, but I don't see Prisma offering the `@Transactional` decorator any time soon until [ES6 decorators](https://github.com/tc39/proposal-decorators) are in the language....

Had the same problem, but I think I solved it! It seems that when using `express-promise-router`, you *have to* pass a string to the @Get() (or any) decorator. e.g. this...

Is this actually something that _can_ be easily supported? The web client would have to act as a real publisher/subscriber and be able to connect to an actual message broker...

> How do I handle checking if adding metadata breaks the transaction decorator Personally, I would add a simple transaction test (using the mock adapter) for a method that accepts...