loading flag should be true on initial network request of cache-first policy

Intended outcome: Using the default ‘cache-first’ fetchPolicy, the client will need to load data from the network since the cache is empty initially. In order to display loading indicators, I need to be able to distinguish a network response from a cache response via the loading flag.

Actual outcome: All responses using the cache-first policy have loading set to false. Hence no distinction is possible.

How to reproduce the issue: Create a query with ‘cache-first’ fetchPolicy and inspect the loading prop of the response object.

Version

• apollo-client@1.2.2

[danielddb]

The docs at https://www.apollographql.com/docs/angular/basics/queries.html#basics state “The observable will only emit once when the query is complete, and loading will be set to false unless you set the watchQuery parameters notifyOnNetworkStatusChange or returnPartialData to true.”, but I’ve found that even when setting notifyOnNetworkStatusChange to true, it does not. Also, the property returnPartialData doesn’t exist. Using apollo-client 2.4.2. Setting fetchPolicy to cache-and-network made it work. But as this issue states, it should now. 😕

I’m having exactly the same issue on 2.4.2 and could only get it to work using cache-and-network too.

[patricknazar]

The docs at https://www.apollographql.com/docs/angular/basics/queries.html#basics state “The observable will only emit once when the query is complete, and loading will be set to false unless you set the watchQuery parameters notifyOnNetworkStatusChange or returnPartialData to true.”, but I’ve found that even when setting notifyOnNetworkStatusChange to true, it does not. Also, the property returnPartialData doesn’t exist. Using apollo-client 2.4.2. Setting fetchPolicy to cache-and-network made it work. But as this issue states, it should now. 😕