Alex / KATT

This feature has been added in the [`next`-branch](https://github.com/trpc/trpc/tree/next) of tRPC, meaning it is available in v11 of tRPC. It's possible to start using it _today_, have a look at the...

Cool. I'm optimistic we could support this. As a workaround, anyone who approaches this problem should be able to achieve the same perf gains using the SOA-approach: https://github.com/trpc/trpc/tree/main/examples/soa (or the...

I'm actually unsure if this would've actually pushed the needle the same way the refactor to the SOA approach. The culprit is likely not trpc itself but rather each router's...

In the WS example it works as we use cookies for auth, but agree it would be nice to do this

Feel free to submit PRs to this -- I'm happy with any solution that copies existing solutions out there like how Apollo, urql, or Relay does this

Hey guys I've made an example of how you can do WebSocket auth by leveraging that the `url`-property of `createWSClient()` can be a callback. Is this what people are looking...

& if we did do `connectionParams` as a first class citizen, do we expect those to be sent as a query string? AFAICT, that's the only solution to to "fake"...

Yeah, I see how it's preferable with a message, I did it this way initially to be able to use the same solution across SSE and WS

I've made it work with an initial message now instead, just awaiting some reviews

This feature has been added in the [`next`-branch](https://github.com/trpc/trpc/tree/next) of tRPC, meaning it is available in v11 of tRPC. It's possible to start using it _today_, have a look at the...