Skip to content
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

CacheResolver #184

Merged
merged 2 commits into from
May 17, 2013
Merged

CacheResolver #184

merged 2 commits into from
May 17, 2013

Conversation

havvg
Copy link
Contributor

@havvg havvg commented May 13, 2013

fixes #183

@havvg
Copy link
Contributor Author

havvg commented May 15, 2013

@iamdto @Maxwell2022 @lsmith77 What do you think about it?

*/
public function clear($cachePrefix)
{
// TODO: implement cache clearing
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is tricky, as the $cachePrefix does not correlate to a given scheme to reflect a subset of targetPaths on the resolver in use. I think, if someone needs this, he would need to add a sub-class and override this method according to the resolver in use.

@iamdto
Copy link
Contributor

iamdto commented May 16, 2013

Didn't test it, but looks good so far.

@havvg
Copy link
Contributor Author

havvg commented May 17, 2013

We activated it, and it's working nicely, so I'm gonna merge the current version for a start.

havvg added a commit that referenced this pull request May 17, 2013
@havvg havvg merged commit 3d7ca21 into liip:master May 17, 2013
@havvg havvg deleted the feature/cache-resolver branch May 17, 2013 08:18
@iamdto
Copy link
Contributor

iamdto commented May 17, 2013

Thanks 👍 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Level: New Feature 🆕 This item involves the introduction of new functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CacheResolver
2 participants