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
If it's not an obvious bug or obvious user error, I can try to create a minimal repro.
The gist of it is that I have conditionally rendered components (like modals) using useQuery(). If I render that component, it adds a query to "Active Queries". If I destroy the component, the Active Query stays there. The same thing happens if I change the props to the component (which changes the variable passed to the query).
I don't have a massive memory leak, so I don't expect that the queries are all actually sitting there, active, but it makes the extension very difficult to use.
Desktop (please complete the following information):
OS: Windows 10
Browser: Firefox (happens with Chrome too)
Browser version: 91.6.0esr
Extension version: 4.0.0
The text was updated successfully, but these errors were encountered:
Intended outcome:
Active Queries should not multiply when the component is re-rendered
Actual outcome:
Every time a component that uses
useQuery()
is unmounted and re-rendered, the query is appended to the list of "Active Queries"How to reproduce the issue:
I posted some more context/questions on the forums here: https://community.apollographql.com/t/im-new-to-apollo-ive-built-a-functional-app-server-client-and-now-i-have-a-few-questions-about-queries-caching-and-dev-tools/2793/2
It's entirely possible that this is user error, but as I've not received any responses on the forums, I'm creating an issue here as well in case it is in fact an extension issue.
If it's not an obvious bug or obvious user error, I can try to create a minimal repro.
The gist of it is that I have conditionally rendered components (like modals) using
useQuery()
. If I render that component, it adds a query to "Active Queries". If I destroy the component, the Active Query stays there. The same thing happens if I change the props to the component (which changes the variable passed to the query).I don't have a massive memory leak, so I don't expect that the queries are all actually sitting there, active, but it makes the extension very difficult to use.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: