oRPC Hey API Integration

To generate an oRPC contract from an OpenAPI specification, you use this integration to automatically parse your OpenAPI definitions and output the corresponding oRPC contracts for server implementation or type-safe client creation.

Yes, you can convert an existing Hey API client into an oRPC client. This integration supports direct client conversion, allowing you to transition your current Hey API clients to the oRPC framework seamlessly.

Generating oRPC contracts from OpenAPI specifications allows you to automatically create type-safe definitions. You use these generated contracts to implement the service on your server or build type-safe clients for client development.

Yes, this integration relies on the @orpc/hey-api and openapi-generator dependencies to perform contract generation and client conversion, ensuring accurate type translation between OpenAPI specifications and oRPC structures.

The best way to use generated oRPC contracts for server implementation is to run the contract generation process first. You then apply these contracts directly in your server code to enforce the OpenAPI specification structure.