TanStack Query – invalidateQueries resets filtered data
useQueryuseMutationtypescript
Hi forks,
I’m facing an issue with TanStack Query query keys.
Current setup:
*Initial listing is fetched using useQuery with: *
*When filters are applied (POST API), I update the same cache using: *
Filtered results show correctly.
Problem:
After integrating a favorites (like/unlike) API, I call
This prefetches the initial unfiltered data instead of keeping the currently applied filtered list.
Questions
What is the recommended way to handle this?
Should filtered data have a separate query key?
Should filters be part of the query key?
Or should favorites update the cache without invalidating?
I’m facing an issue with TanStack Query query keys.
Current setup:
*Initial listing is fetched using useQuery with: *
queryKey = QueryKeys.CATEGORY_LIST(“mobiles”).*When filters are applied (POST API), I update the same cache using: *
queryClient.setQueryData(...).Filtered results show correctly.
Problem:
After integrating a favorites (like/unlike) API, I call
queryClient.invalidateQueries(QueryKeys.CATEGORY_LIST("mobiles")).This prefetches the initial unfiltered data instead of keeping the currently applied filtered list.
Questions
What is the recommended way to handle this?
Should filtered data have a separate query key?
Should filters be part of the query key?
Or should favorites update the cache without invalidating?
