Replies: 1 comment
-
Update - I was finally able to figure it out. I was able to have the infinite query caching working just fine inside a sandbox environment and realized the issue was with server side rendering which caused the app to re-create the initial QueryClient instance over and over. |
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
-
Hi, my React app is using both useQuery and useInfiniteQuery. When using react-query-devtools, I can see the cache is being set and cleared with no issues for queries that used useQuery to fetch the data. But any data fetched using useInfiniteQuery is not setting the cache and I am not able to use invalidateQueries to clear it either. We were previously using a SUPER old version of React query (not Tanstack) and this pattern was working.
I have tried various different solutions with no luck. Below is the exact scenario I am trying to solve for and my current implementation.
Scenario:
Query list of orders. In a modal, delete an order and invalidate the query so that it refreshes and the list of orders does not contain the deleted order. Important to note, the modal does not have access to the useInfiniteQuery refetch method.
Current code:
List page - using this solution, I can see the cache is set in react-query-devtools but it's inactive
Delete modal
Beta Was this translation helpful? Give feedback.
All reactions