-
Notifications
You must be signed in to change notification settings - Fork 887
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
remove the token from the ICacheBuster api #1583
Conversation
This exposes the QueryStringCacheBuster and PathSegmentCacheBuster public APIs alongside the md5-variants. These should be more cleanly subclassed by people wishing to extend their implementations.
.. versionadded:: 1.6 | ||
""" | ||
def __init__(self): | ||
PathSegmentCacheBuster.__init__(self) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason you're calling these explicitly instead of just doing:
def __init__(self, *args, **kwargs):
super(PathSegmentMd5CacheBuster, self).__init__(*args, **kwargs)
Should be less fragile that way as long as you make sure you pull out any kwargs/args that the class whose defining the __init__
adds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah alright. Fixed.
Added a comment about the particular implementation, but otherwise this looks good to me. |
LGTM |
remove the token from the ICacheBuster api
This exposes the QueryStringCacheBuster and PathSegmentCacheBuster
public APIs alongside the md5-variants. These should be more cleanly
subclassed by people wishing to extend their implementations.
Fixes #1582.