Avoid null keys with enabled option

[BillySemana]

Hello everyone 👋 ,

I don't know if it's the expected behaviour but I have "null" keys in my cache even when using the enabled option.

I'm using a hook for fetching a collaborator by id

const useCollaborator(id?: number) {
  return useQuery(["collaborators", id], fetchCollaborator, {
      enabled: !!id
  })
}

I still have a cache with the following keys ["collaborators", null]
I was expecting to not having a cache at all when id is undefined.

Is there a way to avoid that ?

[TkDodo]

The query should show up as disabled in the devtools. There is no way to avoid that, because the query has been created, even if it's disabled. You could pre-fill it with initialData, and you can trigger a fetch with refetch returned from useQuery even if the query is disabled. Does the cache entry bother you?

[mossen]

In my case what bothers me is I cannot get the data if the cache entry is there, compare following entries:

const versionData = queryClient.getQueryData(
    [QueryKeys.VERSION],
    { exact: false },
  );
  const projectConfigData = queryClient.getQueryData(
    [QueryKeys.PROJECT_CONFIG],
    { exact: false },
  );

projectConfigData is undefined as the key confuses the filter, I need to get the ["project-config","rb.gcf.project-config.csv"] but it works for versionData