weixin_39564605的博客

Describe the bug When fetching a query using "cache-and-network" policy the effect is the same as when using "network-only" policy, i.e. the data is only available after the request is complete event though cached result should be available instantly.

Steps to reproduce Steps to reproduce the behaviour: 1. Set up server that responds to query with 1s delay 2. Set up client that uses the query to display some data and uses requestPolicy: "cache-and-network" 3. Use the client in a way that makes the query execute multiple times e.g. navigating between pages 4. verify whether query data is available instantly from the cache or not

Expected behaviour After executing query for the first time its cached, so for any consecutive executions query result is retrieved from cache first (also request is sent to update cache if needed). The data returned from the query result is not undefined.

Actual behavior Each execution of the query behaves like "network-only", no data from cache is extracted. The data returned from the query result is undefined until request completes.

Additional context - using urql v1.6.3 - using default cacheExchange - using react v16.11.0 - using hooks API (generated via https://www.npmjs.com/package/-codegen/typescript-urql) - not running any mutations that would invalidate the cache - urql devtools show that data is cached, but report "This result wasn't served from cache" anyway - query has no variables - when using the default "cache-first" policy the data is cached and retrieved from cache properly

related piece of code when I encountered this:

  const [{ data, error }] = usePostsListQuery({
    requestPolicy: "cache-and-network",
  });
  const posts = data && data.posts;

  if (error) return <h3>Error!</h3>;
  if (!posts) return <h3>Loading...</h3>;

  return (...);
  ...

I get Loading... each time until backend responds with data.

该提问来源于开源项目：FormidableLabs/urql