No difference beetween `cache-and-network` and `network-only` strategies!

I think the cache-and-network strategy doesn’t work properly and acts similar to network-only.

What To Expect

1. apollo sends two queries to cache and network in parallel.
2. if doesn’t exist in cache waiting for network and store in cache for next query.
3. if exists, render data and wait for network in background for syncing data.

but in step 3 :

apollo doesn’t render cache data Immediately until network data is received. This is not fast and behaves like network-only strategy.

[lassesteffen]

I just saw that if you use notifyOnNetworkStatusChange: true it works for me and does return the cached data on the first return

[fforres]

This is the solution we are using to expose a refetching prop so we can control rendering behaviour better @wminshew @foad-salawati

import type { OperationVariables, QueryResult } from "@apollo/react-common";
import type { QueryHookOptions } from "@apollo/react-hooks";
import { useQuery as useApolloQuery } from "@apollo/react-hooks";
import type { DocumentNode } from "graphql";

export function useQuery<TData = any, TVariables = OperationVariables>(
  query: DocumentNode,
  options?: QueryHookOptions<TData, TVariables>,
): QueryResult<TData, TVariables> & {
  refetching: boolean;
} {
  const response = useApolloQuery<TData, TVariables>(query, options);
  return {
    ...response,
    refetching: response.networkStatus === 4,
  };
}

Then you can do

const { refetching } = useQuery(aQueryDocument);

I know it’s not a real solution to the issue, but maybe it helps as a patch