-
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
Support marking fetches as not to be served from cache #183
Comments
I've been working on a WIP branch for implementing this, but I've found a few cases that cause problems:
After thinking about it I don't think this fits with the Fetch execution model and is best implemented with a custom cache in userland that discriminates the 'Data' instances that you don't want cached. It should be relatively easy to do, happy to provide guidance. |
@purrgrammer is this something we need to include in the docs? And perhaps even elaborate with a basic snippet on how to do this in userland? |
I'm going to write a list of "Use fetch if" and "Don't use fetch if" in the docs to clarify what the library is suited for. Good point!
Sure, I'll write an example and submit a PR. |
No description provided.
The text was updated successfully, but these errors were encountered: