feature request: openrpc generation

[devtempmac]

openrpc is something like swagger/openapi for jsonrpc

similar work:
yerpc (https://github.com/chatmail/yerpc) has rust<->ts and openrpc, but I couldn't get its axum example code to connect to the browser :(

[andogq]

Thanks for your issue! Is there a problem in particular that you are facing that is solved with openrpc?

Qubit already provides a TS client, so there shouldn't be any need to generate one from an openrpc spec (unless there's a feature that the client is missing).

[devtempmac]

not a problem, but I was hoping to extend qubit to output openrpc spec and use it to codegen other language clients (eg. kotlin, python, swift)

[andogq]

This sounds reasonable enough, and appears to be inline with the rest of the project to implement. Some thoughts:

• Currently ts-rs handles all of the type generation from Rust structs into TS types. Another component will have to be introduced to generate the OpenRPC schema for each type (of which I'm sure there's plenty that exist), however care will need to be taken to ensure that the types generated from both sources match (for instance, ts-rs can understand certain serde attributes).
• I've been considering bringing the API and generated types inline with tRPC, so that qubit can take advantage its ecosystem and popularity. This would provide a significantly better TS client (just use the tRPC client, but point it at the generated types). The downside of this is that the protocol differs for JSONRPC (not significantly, but it is different). This could be addressed by providing server 'adapters', capable of supporting JSONRPC, tRPC, and any other protocols that may come in the future (eg Qubit without JSON-RPC? #92).

In short, I'm quite keen on this feature. Some work will be needed to have the schemas correctly generated. I unfortunately can't promise if/when I will get to this, however any PRs or investigation would be greatly appreciated!