Hugh Willson

@Borales @smolinari We'll have something to share hopefully very soon! The beta is almost ready; we just have a few more edge cases to address, as well as additional tests...

👋 @dylanwulf - just touching base on this; do you think this is still a significant issue with current day `@apollo/client`? We're happy to dig into this if so.

`__resolveType` is a [`graphql-tools`](https://github.com/apollographql/graphql-tools) feature, and is not currently supported with local resolvers. Marking as a feature request - thanks!

Related to https://github.com/apollographql/apollo-link-state/issues/138.

We'll look into expanding the arguments/options passed to the mutation `update` function. `context` and `variables` have already been added (since this FR was created): https://github.com/apollographql/apollo-client/pull/7902 If you have suggestions for...

@pashazz The `alpha` is currently usable, but the plan is to get the final release of Apollo Client 2.5 out next week.

Any chance you can provide a small runnable reproduction that shows what you're trying and isn't working? There are a few important details missing here that will help with troubleshooting...

@eric-burel We're working on a new version of `apollo-link-state` that should accommodate this. The new approach is no longer Apollo Link based, and is instead wired directly into Apollo Client....

Great, thanks for the feedback @eric-burel! Re: replacing a resolver with the same name; yes, that's doable with the new API. More details soon - thanks!

Interesting idea @fbartho! > The problem is that if we leave the Query marked as cache-and-network, sometimes Apollo chooses not to hit our link-state resolver. This sounds like a bug...