apollo-client: @client(always:true) doesn't work 🐛

Closing since we just published the final version of apollo-client@2.6.0 to npm, including some improvements to the functionality discussed in this issue. While there may still be related issues that are worth addressing, we are happy to continue those discussions in new issues. See CHANGELOG.md if you’re curious about the other changes in this release.

“always:true” should mean always as in always 😄

Still an issue.

@hwillson @benjamn can someone please follow up? I’m also experiencing issues with this.

resolvers only seem to run for preloading values in the cache and not 100% of the time.

I tried out 2.6.0-beta.2 and in my use case (running a query offline) @client(always:true) is still not triggering the local resolver, it’s just reading directly from the cache. Let me see if I can put together an example of this

As @hwillson indicated above, this problem should be fixed if you update apollo-client to version 2.6.0-beta.2 (just released): https://codesandbox.io/s/q7n4z9zp96

We’re not quite ready to release apollo-client@2.6.0 officially, but that will happen faster if folks can help us test the beta versions. 🙏

seems like, it still isn’t resolved !

the resolvers are only called the first time and never again.

for the time being I using a similar approach to @supercranky 's cachebust hack…

but its so ugly !

Ohh sorry! I hit the wrong button hehe

Still an issue with "apollo-client": "2.6.2"…

The error is still reproduced with latest client https://codesandbox.io/s/alwaystrue-0c0h0

@supercranky Let’s continue the discussion of offline refetches in https://github.com/apollographql/apollo-client/pull/4840 (warning: that change may not be safe for 2.6.0, given the current release candidate status, but could land soon afterward).

Made a new example with some cache busting (added an unused counter variable to the query) https://codesandbox.io/s/1vx1nn7m7q

This works (even offline), so I’m guessing that there is some kind of memoization going on in either react-apollo or the apollo client

@nuragic Can you re-open please? I mean it’s still an issue

Also facing this using a mixed schema (remote and local)

    annotations {
      id: _id
      xmlIDTag
      content
      type
      position @client(always: true)
    }

Does trigger the first time, once gets cached it doesn’t execute the resolver anymore.

This may be an issue with putting the @client(always: true) directive on a field that has its own selection set, rather than leaf fields, though I was under the impression both approaches should work:

export const CLIENT_QUERY = gql`
  query {
    apollo @client(always: true) {
      cool
      bug
    }
  }
`;

We (@hwillson and I) will investigate!