Apollo seems to hit the network consistently, even if "cache-only" is the fetch policy

[glebdv]

Trying to figure out if im doing something wrong here.

Query: (we're using codegen to generate types from the schema)

ROOT_QUERY cache:

The component is basically a two part radio group toggle that either fetches all availableHospitalsForAppointment with deptId: null or per department scpecific hospitals.

However, it seems that every time the call is made, a network request is always made, and always hits the backend.

All of the below calls are GetAvailableHospitalsForAppointment queries

we have custom typePolicies for certain things, but none for that graphtype

any thoughts on why this could happen? I set it cache-only just to check, but it always seems to hit the backend, otherwise we have it at cache-first

[glebdv]

does it maybe have anything to do with the fact that we are refetching the query?

[glebdv]

ok like 99% convinced its because of that; is there any way of setting the fetch policy or will I have to transform this to a lazyQuery?

[glebdv]

100% convinced its that. I just changed it to a lazyQuery that fires on load although I try to avoid the useEffects as much as I can

[phryneas]

Yes, it's due to the refetch - there's no more explicit way of saying "I really want this to hit the network layer" than calling refetch.

Question: why do you not skip any useEffects and just set a state with the variables you want to use for your query? The component will rerender and the useQuery hook will execute for those new variables.

[glebdv]

good point, I did exactly that,thank you!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.