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
This happens since we are always expecting the query to actually have one of three state : loading, error or data, but when we pass skip the query doesn't actually get executed and we don't get any of these states which trigger the error log.
Expected behaviour
The query component should be able to support the skip option without throwing a console error, since it's also a valid state of the query.
The text was updated successfully, but these errors were encountered:
We could enhance it to return a different type including this 4th state when skip is set.
An alternative would be to simply not allow skip and refer to using the original Query component from Apollo like we do for notifyOnNetworkStatusChange.
Problem
Currently, when using the
skip
option (https://www.apollographql.com/docs/react/essentials/queries.html#props) on aQuery
component, we get the console error :An unexpected Query sidecase happened where no valid union type could be found, please file an issue for this.
This happens since we are always expecting the query to actually have one of three state :
loading
,error
ordata
, but when we passskip
the query doesn't actually get executed and we don't get any of these states which trigger the error log.Expected behaviour
The query component should be able to support the
skip
option without throwing a console error, since it's also a valid state of the query.The text was updated successfully, but these errors were encountered: