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
Describe the bug
When using stock.get() the Future resolves after the API query, rather than resolving from the cache, querying, and then updating the cache.
Expected behavior
On refresh, return data for [key] if it is cached otherwise will return fresh/network data (updating your cache).
Screenshots
The fetcher being used to demonstrate the query:
Describe the bug
When using
stock.get()
the Future resolves after the API query, rather than resolving from the cache, querying, and then updating the cache.Expected behavior
On refresh, return data for [key] if it is cached otherwise will return fresh/network data (updating your cache).
Screenshots
The fetcher being used to demonstrate the query:
The method testing the request (using a Cubit):
And the output:
Package info:
Additional context
I expect that regardless of whether the cache exists, the query should be executed to refresh the cache.
The text was updated successfully, but these errors were encountered: