James Berry

Hi @o-dasher, currently `trpc-openapi` OpenApiV3 document currently only supports `application/json` as `requestBody`s. We can add support for other `Content-Type`s if required, what do you need/what is your use-case?

We should ensure that `@trpc/server` can handle alternate `Content-Type`s such as `application/octet-stream`, before supporting this functionality in `trpc-openapi`. There is an open tRPC issue here: https://github.com/trpc/trpc/issues/1937

> Is enabled necessary at all? Thanks @sachinraja - you're right. But I just want to make sure that it's really hard for developers to accidentally leak endpoints into their...

* Meta `openapi.enabled` will now default to `true` if unspecified. * Meta minimum requirement is now just `{ method: string, path: string }`. Will be released in next major `v1.0.0`....

From my understanding, the main use-case for `trpc-openapi` is exposing only a _subset_ of procedures to third-party consumers AND dedicated endpoints for receiving webhooks. For this reason we decided to...

@mohsen1 are you aware that supplying an `output` schema is also a requirement for `trpc-openapi` enabled procedures? We could add a property to opt-in everything at once (ie. `unsafe_defaultEnabled`), however...

Hi @SeanCassiere - thanks for this! We can add this `fastify` adapter to the `trpc-openapi` repo if you want to open an PR. Happy to work with you on this...

I actually forgot to mention [`sachinraja/uttp`](https://github.com/sachinraja/uttp) when I wrote my earlier message. This could be a good solution - any thoughts?

Hi @SeanCassiere, sorry for the _super_ late reply! > Or shall I do what I'm currently doing by remapping the request and reply the methods to match what is used...

Looks great, thanks @SeanCassiere 🙌. Just opened [this PR (#170)](https://github.com/jlalmes/trpc-openapi/pull/170) on your behalf - I will take a closer look over the weekend!