Michael Joseph Rosenthal

I just published version `0.0.5`, which should solve this issue. Leaving open to remember to pin the dependency

@mainawycliffe yeah, and maybe have some helper on `QueryResult` for merging them, and some sane defaults

@mainawycliffe the docs need to be reworked for lib level exceptions - idk when I'll get around to it

Added a basic mechanism here – https://github.com/micimize/graphql-flutter/tree/fetch_more_errors I still think the full result merge approach is better though.

The dead link was about how apollo wanted to deprecate some aspect of their api. It would make sense to have an api for getting the most recent instance of...

@smkhalsa we still want to [maintain unique ids](https://github.com/apollographql/apollo-client/blob/57a881894f7924bf3e091a62b913ca65a966ae3c/packages/apollo-client/src/core/QueryManager.ts#L74-L78), because the lifecycles of two distinct operations with the same docs + variables will be different. We can just [find the relevant...

It seems we really should have first-class support for cookies. My first inclination is a [custom link](https://gist.github.com/micimize/62781aac9840a7b11405c3fda51a7e62), but that might be awkward In #531 @chynamyerz suggests adding it as a...

@emme1444 there have been no updates, no

Would just exposing client connection state work here? ```dart class WebSocketLink extends Link { //... Stream get connectionState => _socketClient.connectionState; } ```

One potential stop-gap for this is doing something like the following on the v4 beta: ```dart SocketClientConfig( onConnectOrReconnect: (socket) async { socket.stream.doOnError(...) }, ) ```