Should data from useQuery ever be undefined for cache-hit in react?

[austin43]

Hello,

I have a question about how graphcache operates with react.

Using debugger, I see the flow of a useQuery hook with a cacheHit go something like this:

initial render -> data: undefined, fetching: true
useQuery cache-first -> results in cache hit
second render -> data: cached result, fetching: false

This same flow repeats each time I render the view.

The expected behavior I have for a cache hit would be:
initial render -> useQuery cache-first -> results in cache hit -> data: cached result, fetching: false

Is the first scenario I described expected, or am I missing something? My assumption would be that the cache is read synchronously, and the data always defined if there is a cache hit. Thanks in advance for any comments, and for the continued work on this fantastic library 😄

[JoviDeCroock]

Hmm this should only occur if you have an asynchronous exchange in front of your cacheExchange

[austin43]

That was it! I had authExchange in front of it. Thank you for the quick reply.