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
Is your feature request related to a problem? Please describe.
My feature request is related to a problem because the current behaviors doess not allow users to invalidate the cache, which can lead to incorrect or outdated information being returned. By adding a cache invalidation feature, users can ensure that they are always working with up-to-date information.
Describe the solution you'd like
I propose adding a new function to the fetchp called invalidateQuery() that allows users to invalidate the cache for a specific query. This function would take a query parameter as input, and would remove any cached results for that query from the cache. This would allow users to ensure that they are always working with the most up-to-date data, even if the cache has become stale or outdated.
Example at bellow:
response.invalidateQuery()
open to debate
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
My feature request is related to a problem because the current behaviors doess not allow users to invalidate the cache, which can lead to incorrect or outdated information being returned. By adding a cache invalidation feature, users can ensure that they are always working with up-to-date information.
Describe the solution you'd like
I propose adding a new function to the fetchp called invalidateQuery() that allows users to invalidate the cache for a specific query. This function would take a query parameter as input, and would remove any cached results for that query from the cache. This would allow users to ensure that they are always working with the most up-to-date data, even if the cache has become stale or outdated.
Example at bellow:
open to debate
The text was updated successfully, but these errors were encountered: