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
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
After a mutation, the refetchQueries prop is used and all queries that have matching names are refetched.
Actual outcome:
After a mutation, the refetchQueries prop is used and the first query for each matching name is refetched.
How to reproduce the issue:
I don't have time to create a reproduction right now, I'm hoping this rings a bell, if not I can create a repro.
Basically, we have several queries with the same name that have slightly different fields, eg. query foo { foo { id bar } } and query foo { foo { id meep } }. Since v2.1 of react-apollo, only one of those queries gets updated.
I should add that changing the name of the queries and adding it to the refetchQueries works around the problem, but I do believe it should not be necessary.
React Apollo has been refactored to use React Hooks behind the scenes for everything, which means a lot has changed since this issue was opened (and a lot of outstanding issues have been resolved). We'll close this issue off, but please let us know if you're still encountering this problem using React Apollo >= 3.1.0. Thanks!
Intended outcome:
After a mutation, the
refetchQueries
prop is used and all queries that have matching names are refetched.Actual outcome:
After a mutation, the
refetchQueries
prop is used and the first query for each matching name is refetched.How to reproduce the issue:
I don't have time to create a reproduction right now, I'm hoping this rings a bell, if not I can create a repro.
Basically, we have several queries with the same name that have slightly different fields, eg.
query foo { foo { id bar } }
andquery foo { foo { id meep } }
. Since v2.1 of react-apollo, only one of those queries gets updated.Version
It used to work before.
The text was updated successfully, but these errors were encountered: