Phil Pluckthun

Hm, I'm not quite sure where in the documentation we talk about that, but I'm not sure whether that's actually supported 😅 I unfortunately don't remember all the mechanics of...

Sorry, I didn't see the pings 😅 I have nothing against looking at some code for this

Definitely a very logical addition to the internals 👍 I'll defer to @JoviDeCroock for a second opinion on this. One thing that's already obvious is that it's a break change,waning...

> Header specified in context.fetchOptions.headers overwrites the headers defined at the client-level Sorry, can you clarify what you're after? There's only one header that's added by default. If you mean...

Closing due to inactivity. I'm still happy to come back to this and discuss what the underlying motivation is, which may mean we'll be able to reopen this :v:

The thing is that there's not a single "moment" a result is given in `urql` and that's a design choice. Rather, once you're dealing with the bindings you're dealing with...

Sorry, I forgot to come back to this here. Basically, as we outlined before, this is a bit of a question between how bindings work and how the core Client...

Yep, that's totally expected behaviour, but with the added difficulty that without knowing how you configured the query, what request policy you're using, how you've set up Graphcache, and whether...

> Do you mind elaborating on what you define as a flag/local state? I'm not quite following the difference here. As a naive consumer, fetching and stale are both "flags"...

@ceefour That's really odd. Mind opening a new discussion thread for that? This usually happens in one of two cases: - You're using `cache-and-network` by default or at the query...