Alex / KATT

I think the (seemingly) proper "call" in contrast to "invocation" is one of the most awe-inspiring things we have achieved with the new API. I don't really mind that it's...

I have spent a lot of time thinking about this & will give a proper write-up of what I think and stronger motivations for the API decisions taken. I truly...

@skovhus It's totally possible to dynamically opt-out of batching for the ones you have: https://trpc.io/docs/links#using-a-splitlink-to-control-request-flow I see something like this It could be something like: ### Client usage ```ts const...

@skovhus have a look at the above (just updated)... not super happy with the API, it's a quite implicit and frail relationship

> Thanks for the proposal. So if I understand this correctly splitLink is running for each procedure? Is a procedure the same as an operation? Correct, an "operation" is a...

Thinking about this a bit more, it might be better to instead move `headers()`-fn to the `httpBatchLink`/`httpLink`/etc, so they can have a bit less confusing signature.. additionally, tRPC isn't tied...

cc @zomars @abhayvatsa @leog The question to answer is _"How do we handle when a specific procedure should be called with custom headers?"_ Please read through the thoughts above 🙏

> > Maybe this shouldn't be possible at all? I thought the proposal was to remove it from the client. > > I assume the common use case if to...

> I don't think that should be tRPC's responsibility @skovhus Similar on how you can pass options to `fetch` however you like. Also with this we're going more into `react-query`...

Could be added, but nextjs is deprecating getInitialProps, harder so with the new router they're planning. Happy to take PRs that enables this on the `next` branch though.