James Berry
James Berry
> Put all tRPC options under `trpc: { ... }` Without thinking too much about it - this would be my choice. It seems like the most simple, clean a...
Like this idea, I'm also not sure how to best handle retrying after an `INTERNAL_SERVER_ERROR` error.
Related https://github.com/trpc/trpc/discussions/658 & https://github.com/trpc/trpc/issues/1937
Top work @sachinraja - this simplifies lots of the existing code which is always great! I think this PR actually has created so many open-ended questions for me. We first...
Just updated description and added tests - ready for review!
### Updates * Normalized method in `TRPCClient.ts`. * Deduped HTTP subscription error message. * Added opt-out for server via `methodOverride.enabled: false`. * Fixed tests & added test for opt-out. ###...
Hi @jrmyio. The `input` validation should only be used for parsing request input (e.g. check that `userId` is defined and is a `number`). Any data fetching or additional logic should...
Hi @jrmyio. It looks like the use-case you mentioned above is best suited to the `.middleware(...)` utility. You can read more about it here: https://trpc.io/docs/middlewares#raw-input. Let me know what you...
Regarding `Simplify HTTP-responses`: - This would means moving away from the JSON-RPC spec, are we ok with this? - Would this also mean removing `id: 1` from the HTTP-request? -...
continued... * Moving towards a Slack-style API might make public-facing TRPC APIs easier to use and drive greater adoption (cc. https://github.com/trpc/trpc/issues/755)