Phil Pluckthun

### Implementation Plan Only one data structure is needed to track all fields: ```ts interface Field { activeOperations: number, parentFields: Set, returnTypeName?: string, fieldName: string, arguments: any, // NOTE: In...

This is intended behaviour. We reuse the `Client` because we preserve the cache. This is really a basic behaviour of a fetching/state client, so we don't want that cached state...

Closing due to inactivity. Let me know if that helped or if there are more questions you have, or are trying to achieve something specific ✌️

I haven't gotten around to checking this yet but your `Query.getTodos` field is defined as `[Todo!]!`. Invalidating an entity deletes it from the cache, which means that it's not existent...

@sarink: Do you still need help here and does the above make sense, i.e. `[Todo!]!` being defined as required?

Hm, that's true. It's indeed not always feasible to communicate client-side requirements to the schema designers. I suppose, we can't do much about that by changing Graphcache unless this was...

Ready to be picked up but may not be addressed immediately if #964 is also ready to be worked on

It isn't really what we were envisioning here to be completely honest. GraphQL is pretty great because it fits the mental model of componentised apps really well. Ultimately it's a...

I'm wondering however, would it make sense to still provide an Options API if Vue 3 shows the Composition API front and centre. Our ambition was to support mostly Vue...

There's nothing for us to sort out 😅 Either you fetch during rendering or you don't, and that's outside of what urql can decide to do as it's in the...