Revaladting disabeld queiries

[Sergionx]

Describe the bug

On the documentation for
Disabling/Pausing Queries says:

The query will ignore query client invalidateQueries and refetchQueries calls that would normally result in the query refetching.

To my use case this is an incovenience since when I revalidate data (after a form submition for example), there is some disabled queries and this "feature" obligates me to enable all queries if I want to revalidate them

Your minimal, reproducible example

none

Steps to reproduce

1. Disable a query by making enabled = false
2. Call invalidateQueries with the queryKey of the previous query
3. Use Devtools to see that the query in fact was not revalidated

Expected behavior

I would want that invalidateQueries and refetchQueries accept an optional param revaliteDisabled to allow retro-compatibilty for the old behavior. But with this optional param, revalidating could be much more easy

How often does this bug happen?

Sometimes

Screenshots or Videos

No response

Platform

• OS: [Windows, ]
• Browser: [Chrome, Safari, Firefox, ]

Tanstack Query adapter

react-query

TanStack Query version

5.62.0

TypeScript version

^5

Additional context

No response

[TkDodo]

this is how the lib is designed to work, and we’re not gonna change that. disabled=false is not a recommended pattern, as the docs state, as it opts out of many features the lib offers. The recommendation is to disable a query only when some dependencies aren’t ready yet, in which case you would disable it conditionally, not with hardcoded disabled:false.

and if dependencies aren’t ready, triggering that query with refetchQueries would be devastating.

[Sergionx]

Thanks for the response, That is the exact use case when I am disabling a query, when the dependencies are not ready yet. But I have a 10% use case where I have a query that is disabled not for its dependencies but because it is not used yet and the enabled is true when now the data for that query is required