oRPC OpenAPI support

[aidansunbury]

Part of the promise of oRPC is the ability to use it in an OpenAPI compliant way in addition to the typical RPC handling https://orpc.unnoq.com/docs/openapi/getting-started

Three possible ways of going about this in better-t-stack

1. Add OpenAPI setup by default in addition to RPC setup, so that the existing base routes can be used with OpenAPI. Only possible issue with this is it could be a bit confusing to a newcomer which they should use.
2. Add OpenAPI setup as an alternative to RPC setup. The Api layer menu would then look something like "tRPC", "oRPC - rpc setup", "oRPC - openapi setup"
3. Keep the existing oRPC option as is, and add idea (1) of a full setup as a third option. The Api layer menu would then look something like "tRPC", "oRPC ", "oRPC with OpenAPI"

[AmanVarshney01]

yep i like this

I'll add openapi support 💯

[aidansunbury]

I'm also down to do it if you would like @AmanVarshney01. Just would just want your input on which path (1,2 or 3) to go down to support it.

[AmanVarshney01]

I am dropping a big rewrite in like 3 days. It should make the code a bit easier to maintain. lets wait for now. 😃

[AmanVarshney01]

@aidansunbury i tried some things but nothing worked out so no rewrite for now. if you want you can work on the openapi with orpc

• add orpc-openapi as an api option
• add flags and validations
• add orpc's openapi handler for all server 😅
• add openapilink in all clients 😅
• add endpoint for swagger ui too
• make sure it works with better auth's open api too
• update stack builder

this is a lot of work, if you decide to work on it let me know.

[aidansunbury]

I'll get started on it @AmanVarshney01!

[jigz]

#563