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
The situation emerges when I use the refetchQueries option on a mutation but have not yet (due to sometimes varied user paths to the mutation) fetched the particular query named.
It seems preferable to allow a list of invalidated queries to be provided without throwing an error when one hasn't been fetched yet; unless I'm missing something.
The text was updated successfully, but these errors were encountered:
@jasonphillips yes, you're right, we should just ignore the query if it hasn't run yet, or maybe print a warning to the console just to help people discover typos.
I'm running into a situation where this line throws an error by calling forEach on undefined:
https://github.com/apollostack/apollo-client/blob/master/src/QueryManager.ts#L1002
The situation emerges when I use the
refetchQueries
option on a mutation but have not yet (due to sometimes varied user paths to the mutation) fetched the particular query named.It seems preferable to allow a list of invalidated queries to be provided without throwing an error when one hasn't been fetched yet; unless I'm missing something.
The text was updated successfully, but these errors were encountered: