This repository has been archived by the owner on Jun 10, 2018. It is now read-only.
Allow involved processor to change the cache key #508
Closed
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
While many processor can afford using cached assets as long as the sources didn't change some needs to invalidate all the caches between versions. E.g.: currently when Opal is upgraded and a file store is used the cache store folder must be removed (i.e. tmp/cache/assets under rails).
elia
added a commit
to opal/opal
that referenced
this pull request
Dec 7, 2013
Waiting for sstephenson/sprockets#508 to be merged.
|
As of 3.0, the Tilt template interface will be deprecated. Process will just be I think another way I thought to expose this was adding a cache bust to the register api. So Opal could do something like |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
While many processor can afford using cached assets as long as the sources didn't change some needs to invalidate all the caches between versions.
E.g.: currently when Opal is upgraded and a file store is used the cache store folder must be removed (i.e. tmp/cache/assets under rails).
If it's conceptually ok I'll add tests
cc @adambeynon