WIP: feat(useQuery): forward networkStatus

[trojanowski]

Add networkStatus to useQuery result.
Closes #67

WIP: requires ugly hacks in suspense mode

[trojanowski]

Problem with the current implementation is that throwing observableQuery.result() subscribes to it (https://github.com/apollographql/apollo-client/blob/master/packages/apollo-client/src/core/ObservableQuery.ts#L156) and unsubscribes when the result is available. During the unsubscription the isTornDown flag is set (https://github.com/apollographql/apollo-client/blob/cc3706ee76c0de7d56a7936a80ec6e6b96417520/packages/apollo-client/src/core/ObservableQuery.ts#L606) which causes that the NetworkStatus.error is then returned as a value of networkStatus (https://github.com/apollographql/apollo-client/blob/cc3706ee76c0de7d56a7936a80ec6e6b96417520/packages/apollo-client/src/core/ObservableQuery.ts#L186). I was able to workaround it by creating an additional subscription (

react-apollo-hooks/src/useQuery.ts

Line 191 in 92c910f

const fakeSubscription = observableQuery.subscribe(() => {

) which is unsubscribed after the next subscription in the useEffect hook is created (

react-apollo-hooks/src/useQuery.ts

Line 151 in 92c910f

const subscription = observableQuery.subscribe(

). Unfortunately it requires to use unstable API from the scheduler package.

[trojanowski]

I'm closing it - networkStatus is already forwarded in the non-suspense mode. I'll try to add it to the suspense mode when Suspense for data fetching will be considered ready by the React team - maybe it'll be easier then.