Phil Pluckthun

@hawkeye64 your issue was not closed, just fyi, as stated there it was converted to a Q&A discussion: https://github.com/urql-graphql/urql/discussions/3145 The section there I've linked you is the ["No More Default...

I see that it's basically like a "terminating" exchange, but from `urql`'s perspective, no exchange ever has to handle all operations, so it's expected they'll always pass on what they...

Ah, I misread the part where you're instantiating the exchanges. That's indeed where `forward` is used twice. So, the only way to stop that is to wrap the `forward` function...

An implementation already exists, see: #2527 I haven't actually tested and reviewed this myself yet, but it actually never got merged because tests were an issue and due to bandwidth...

Let me know if you'd like any work to be offloaded. I'll try to get around to a first pass review next week. Worst case the PR will get my...

I agree, let's focus on the main API. This is a very similar situation to `@urql/next`, which has recently changed to accommodate React Server Components — however much I think...

I don't know where the `npm_TOKEN` comes from (ending in `d33a`). It may still be an access token by @andyrichardson and _not granular_. In case it is granular, I've disabled...

Alright, I can take care of the extensions keys on Monday. I've got the login credentials for Firefox & Chrome in a 1Password vault, so I'll be able to go...

Updated the RFC to reflect that we don't have to prioritise `gql.tada -> client-preset` (i.e. a reverse codemod) any longer, given that #160 should cover the concerns that may force...

This is on my radar, but to be honest, I'm not a fan of this approach and am rather trying to think of alternative APIs that make composing results easier....