Skip to content

Let's use TRPC #50

@b1n1yam

Description

@b1n1yam

Proposal for using TRPC

By using TRPC for the API we can define our API endpoints as TypeScript functions, eliminating the need for separate API documentation and ensuring type-safety across the entire stack.

Adopting tRPC would bring the following benefits:

Type-Safety: tRPC leverages TypeScript's type system to ensure that the data structures used in the front end and backend match, reducing the risk of runtime errors caused by type mismatches.
Efficient Communication: tRPC uses RPC (Remote Procedure Call) pattern, which allows for more efficient communication between the frontend and backend, reducing over-fetching and improving performance.

Better DX: tRPC provides a better developer experience with features like automatic code generation, TypeScript intellisense, and better tooling support.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions