TRPC: End-to-end typesafe APIs made easy
1–10 of 59 posts
Re: TRPC: End-to-end typesafe APIs made easy
#2The docs don't say anything about the wire protocol - is this based on REST/JSON, or something proprietary? If proprietary, is it spec'd and documented? Support for implementations in other languages?
Re: TRPC: End-to-end typesafe APIs made easy
#3I’ve never used this, but it looks like a very similar idea to Haskell’s Servant library [https://docs.servant.dev/en/stable/]. Could someone who knows more enlighten me as to how correct this comparison is?
Re: TRPC: End-to-end typesafe APIs made easy
#4The docs don't say anything about the wire protocol - is this based on REST/JSON, or something proprietary? If proprietary, is it spec'd and documented? Support for implementations in other languages?
Re: TRPC: End-to-end typesafe APIs made easy
#5> without schemas
What is a type definition if not a schema?
Re: TRPC: End-to-end typesafe APIs made easy
#6Only supports using Javascript/node servers it seems, so sadly it's not really usable for me.
The type exchange seems to rely on shared code between the frontend and the backend to exchange types, rather than using schemas like other systems.
Not implementing server-side events seems like a shame because they're a very capable mechanism for subscriptions without resorting to websockets.
Re: TRPC: End-to-end typesafe APIs made easy
#7Only supports using Javascript/node servers it seems, so sadly it's not really usable for me. The type exchange seems to rely on shared code between the frontend and the backend to exchange types, rather than using schemas like other systems. Not implementing server-side events seems like a shame because they're a very capable mechanism for subscriptions without resorting to websockets.
If you're using OpenAPI, you could use this to generate TypeScript interfaces:
https://github.com/bcherny/json-schema-to-typescript
It works really well
Re: TRPC: End-to-end typesafe APIs made easy
#8Only supports using Javascript/node servers it seems, so sadly it's not really usable for me. The type exchange seems to rely on shared code between the frontend and the backend to exchange types, rather than using schemas like other systems. Not implementing server-side events seems like a shame because they're a very capable mechanism for subscriptions without resorting to websockets.
TRPC is designed for systems where the front and back ends are both TypeScript. In that case it's simpler to have them share code than to go through an intermediary type system such as GraphQL.
Re: TRPC: End-to-end typesafe APIs made easy
#9You can do this with GraphQL too:
https://github.com/graphql-editor/graphql-zeus
I did a 5 min talk about these newer breeds of codegen tools (where it's a single client SDK that does automatic return type inference based on the input args), they're really neat:
https://www.youtube.com/watch?v=7n3MeMFHiMk
(Skip to 2:14 to see the autocomplete/type-safety)
Re: TRPC: End-to-end typesafe APIs made easy
#10If you want a similar experience to this but more optimized for backend development using Go, I've been building https://github.com/encoredev/encore for the past few years!