Null QueryKey values

[cgatian]

I've been looking closely at the cache using the dev-tools and realized there are some query entries that have null or -1 in the query key for instances where the variable was not known at the time of the hook being instantiated.

Example: the id portion of the Profile is not known on initialization of useQuery hook. null is used for the key

While these queries are disabled through the enabled property, I started to second-guess if we were doing it "right".

Some Questions:

• Does it make sense to create a cache entry if the query starts off disabled? Maybe it should only be created once it's been enabled?

• Any advice on how to avoid creating these queries?

• Am I overthinking this, and should just embrace that this is how the library works?

[TkDodo]

Does it make sense to create a cache entry if the query starts off disabled? Maybe it should only be created once it's been enabled?

not possible because you could also pass initialData for example, or other settings that should be immediately available for other observers to be picked up.

also, you can indefinitely keep it as disabled and then call refetch to fetch it :)

Am I overthinking this, and should just embrace that this is how the library works?

yes, it's not necessary to avoid creating these. I've added the disabled label to the devtools to flag these as, well, disabled :)

[cgatian]

Awesome, thank you for your time.