-
Notifications
You must be signed in to change notification settings - Fork 123
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 using a heuristic with the doesitcache
tool
#118
Comments
You might want to change to load heuristics through entry-points to make life simpler (that way someone doesn't shove a bunch of heuristics in one module and get upset when they can't use the path). Alternatively, you might want to something like:
but realistically I think the last one should also take the fully qualified name to avoid naming collisions when using the tool and that would just be |
@sigmavirus24 That is a good idea. The entrypoint bit is a pain in the neck, but |
Yeah, the entry-points are probably a bit of overkill but also make some of these features easier. I'm torn on it personally. |
Any updates on this? Is it up for grabbing or should I leave it be? :) |
Often times CacheControl be confusing b/c something seems like it should be cached, but it is not. There is typically a good explanation for this and work around that comes in the form of heuristics. It would be helpful for the
doesitcache
tool to accept a heuristic.Specificially:
Docs!
Thanks to @sigmavirus24 for the suggestion!
The text was updated successfully, but these errors were encountered: