[WIP] Add a cache busting string generator #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any news on when this is going to be released? |
|
It would be awesome to have this feature to force the browser to load the new assets when something was updated. Now the only way that I found out to overcome this browser cache issue is changing the file name... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to make the generation of the cache busting string configurable with maximum flexibility (that a config can't quite provide).
It introduces a
CacheBusterInterfacethat any CacheBuster can implement with a single method that should return the cache busting string.Easy I guess.
Will talk with @promatik to know if he foresees any downside, but I think we are good.