useQuery with pollingInterval loading state not as expected about apollo-feature-requests HOT 4 OPEN

3.4 and 3.5 dealt with misbehavior in the polling function. It seems like you’re asking about a query that polls for the duration of polling sequence, and knowing that this polling sequence is havppening. If that‘s what you want, then you can use the startPolling() and stopPolling() functions, along with another piece of state which indicates that you’re polling. Something like:

const [polling, setPolling] = useState(true);
const {data, loading, startPolling, stopPolling} = useQuery(MY_QUERY);
useEffect(() => {
  if (polling) {
    startPolling(3000);
  } else {
    stopPolling();
  }
}, [polling]);

// The polling variable can be unset in a long timeout, to achieve the use-case you want, and can be read to determine that we’re in a long poll.

Yes, using a local React state is exactly what we've done to accomplish this. However, this seems like something that ApolloClient should handle.

I’m not really sure that notifyOnNetworkStatusChange will do what you want here.

No, it won't, because as I said that deals only with network-level state.

ApolloClient could easily incorporate this exact type of state-tracking, and from looking at the source code it nearly does already. There are internal functions/handlers that respond to the calls startPolling()/stopPolling(), and between each start and stop, there is a state that we're interested in knowing about - the fact that polling is in progress. This seems like a core state of the Client that should be exposed in its API.

from apollo-feature-requests.

@brainkim
Can you please provide some information about what may have changed in that overhaul?
Is there anything specifically related to what I mentioned about the difference between network-level polling and logical polling state?

from apollo-feature-requests.

3.4 and 3.5 dealt with misbehavior in the polling function. It seems like you’re asking about a query that polls for the duration of polling sequence, and knowing that this polling sequence is havppening. If that‘s what you want, then you can use the startPolling() and stopPolling() functions, along with another piece of state which indicates that you’re polling. Something like:

const [polling, setPolling] = useState(true);
const {data, loading, startPolling, stopPolling} = useQuery(MY_QUERY);
useEffect(() => {
  if (polling) {
    startPolling(3000);
  } else {
    stopPolling();
  }
}, [polling]);

// The polling variable can be unset in a long timeout, to achieve the use-case you want, and can be read to determine that we’re in a long poll.

I’m not really sure that notifyOnNetworkStatusChange will do what you want here.

from apollo-feature-requests.

Sorry to hear you’re having trouble. Can you try 3.4/3.5? I did an overhaul of polling around summer-time so these sorts of issues probably should be fixed in 3.4/3.5 🤞

from apollo-feature-requests.