-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow forceUpdate on POST
requests
#46
Comments
duplicated with #2 |
@kuitos This is not a duplicate of #2. What I believe @peters313 is saying, is that certain methods against an endpoint should remove an existing GET from the cache. For example, if I hit the endpoint like so: This could get more advanced by checking the Status code response, but at the very least, PUT, POST, and DELETE methods are expected to modify the resource, so we should throw away any cached GET. |
For reference, seems that |
sorry for my misunderstand, I think u could control your cache by yourself, as not every project follow the rest api spec, related issue #52 |
would it be possible to allow a forceUpdate (or clear the cache for that matter) to happen on a Post/Put/Delete request? that way if you do simply just local state updates when adding/updating/deleting on the ui but if the component were to mount again, it would see that the cache is no longer there and make the API request to generate a new cache
The text was updated successfully, but these errors were encountered: