Cashew caches HTTP requests and only updates the cached data when it is deleted/expired.
Expected behavior
Cashew retrieves cached data, returns it to the user, and then makes an HTTP request to update the cached data. Once the updated data is available, Cashew pushes it to the user.
What is the motivation / use case for changing the behavior?
I am using @ngneat/cashew to cache HTTP requests in my Angular project.
I would like to know if it is possible to implement the cache and refresh strategy, as exemplified on the angular.io page link
I tried looking for information in the documentation and code, but I could not find any.
I'm submitting a...
Current behavior
Cashew caches HTTP requests and only updates the cached data when it is deleted/expired.
Expected behavior
Cashew retrieves cached data, returns it to the user, and then makes an HTTP request to update the cached data. Once the updated data is available, Cashew pushes it to the user.
What is the motivation / use case for changing the behavior?
I am using @ngneat/cashew to cache HTTP requests in my Angular project.
I would like to know if it is possible to implement the cache and refresh strategy, as exemplified on the angular.io page link
I tried looking for information in the documentation and code, but I could not find any.
Environment