You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if it would make more sense for requestPolicyExchange to run after the cacheExchange, and instead of comparing the staleness of the operation--compare the staleness of the result.
For example, I have a query that returns a list of activities. I also have a query that returns a particular activity by id. These are different operations, so even if the activity query gets a cache hit (from not-stale-data obtained via the activities list query) the call still get upgraded to cache-and-network.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I wonder if it would make more sense for requestPolicyExchange to run after the cacheExchange, and instead of comparing the staleness of the operation--compare the staleness of the result.
For example, I have a query that returns a list of activities. I also have a query that returns a particular activity by id. These are different operations, so even if the activity query gets a cache hit (from not-stale-data obtained via the activities list query) the call still get upgraded to cache-and-network.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions