ReactQueryDevtools renders on the page in the closed state #1948
Unanswered
KatsiarynaMashokha
asked this question in
Q&A
Replies: 2 comments 2 replies
-
interesting. are you able to pinpoint the code change that is different between the two versions? We can try going back to the v2 behaviour, I'm not sure why that was changed though |
Beta Was this translation helpful? Give feedback.
2 replies
-
generally, devtools are kept rendered because they have local state (filers, sorting), and that would get lost with unmounting. However, I made a PR that stops subscriptions to the queryCache while they are closed to solve the perf issue in closed state, please see: #2045 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, I have the following question. I noticed some changes to
ReactQueryDevtools
: when it was a separate packagereact-query-devtools
with react-query v2, in the closed state it did not render on the page. After migrating to react-query v3 I can see thatReactQueryDevtools
are rendered on the page in closed state (I can see that classReactQueryDevtoolsPanel
has an opacity of 0 for closed state). Is it intended for them to be always present even in the closed state?The reason why I'm bringing this up is that react query dev tools are being constantly rendered in the closed state that makes the UI irresponsive for a few seconds. A thing to note is that we use huge query keys for
useQuery
(which we probably need to change as well, not sure how to yet though), and those keys seem to cause rerendering of react query dev tools after every button click in the UI and block it for a few seconds. However, we didn't encounter this kind of behavior withreact-query-devtools
and react-query v2.Beta Was this translation helpful? Give feedback.
All reactions