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've got a situation where sometimes the GET request returns successful but the data is empty. This means subsequent requests return a cached empty object.
I can force a re-GET by setting the options.caching.ttl = 0 however, from what I could tell in the code, this also means the results will not be stored.
I'd like a way to force a new fetch to be made, regardless of the TTL on the existing cache, and when the request is complete, store it as normal with the normal TTL already set.
Is there an existing way to do this, am I going about it wrong, or do you agree this would be a useful feature? (If you agree, then I am willing to submit a pull request, just wanted to make sure it was necessary first).
The text was updated successfully, but these errors were encountered:
I've got a situation where sometimes the GET request returns successful but the data is empty. This means subsequent requests return a cached empty object.
I can force a re-GET by setting the
options.caching.ttl = 0
however, from what I could tell in the code, this also means the results will not be stored.I'd like a way to force a new fetch to be made, regardless of the TTL on the existing cache, and when the request is complete, store it as normal with the normal TTL already set.
Is there an existing way to do this, am I going about it wrong, or do you agree this would be a useful feature? (If you agree, then I am willing to submit a pull request, just wanted to make sure it was necessary first).
The text was updated successfully, but these errors were encountered: