You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many cases can trigger this one. e.g. Search topic for two times with different search text that both has zero search result, the second query will be stuck with loading = true and networkStatus = 1 forever.
Possible Root Cause
It's a apollo-client bug according to the community, might be fixed in V2.2.8.
Workaround
Apply following graphql option within Vulcan withList HOC
notifyOnNetworkStatusChange: true
withList HOC does not provide direct access to graphql option, we have three ways to do it:
Put it directly into withList.js
Modify Vulcan's package.json to use apollo-client beyond V2.2.8
Bug Description
There are many cases can trigger this one. e.g. Search topic for two times with different search text that both has zero search result, the second query will be stuck with
loading = true
andnetworkStatus = 1
forever.Possible Root Cause
It's a apollo-client bug according to the community, might be fixed in V2.2.8.
Workaround
Apply following graphql option within Vulcan withList HOC
notifyOnNetworkStatusChange: true
withList HOC does not provide direct access to graphql option, we have three ways to do it:
Reference
apollographql/apollo-client#1186
apollographql/react-apollo#1397
apollographql/react-apollo#1385
The text was updated successfully, but these errors were encountered: