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

Consolidate advanced-cache.tpl.php In a Future Release #151

Closed
jaswrks opened this issue May 9, 2014 · 6 comments
Closed

Consolidate advanced-cache.tpl.php In a Future Release #151

jaswrks opened this issue May 9, 2014 · 6 comments
Assignees
Milestone

Comments

@jaswrks
Copy link

jaswrks commented May 9, 2014

There are a growing number of routines shared between both the advanced-cache.php handler constructed by advanced-cache.tpl.php and the core plugin class. I think in the future it would be nice to create a common class that could be refactored to support both of these phases (i.e. it would contain all of the routines that both classes can share). This way we can avoid the duplication that we have now.

I think it would be a good idea for us to work on this sometime in the near future so we can catch it before things really get out of hand; i.e. as QC continues to grow this likely to become a bigger and bigger issue in terms of the amount of code that is being duplicated. It's leaving too much room for error in my view.

The same is true for QC lite vs. Pro; although I'm not sure what we can do about that.

@jaswrks
Copy link
Author

jaswrks commented May 9, 2014

@raamdev
Copy link
Contributor

raamdev commented May 9, 2014

Great idea! I also noticed that duplication while working between advanced-cache.tpl.php and quick-cache.inc.php. I'm glad you brought this up. I'll add this to the Future Release milestone to work on after the next release.

@raamdev raamdev added this to the Future Release milestone May 9, 2014
@jaswrks
Copy link
Author

jaswrks commented Jun 9, 2014

@raamdev Would you like any help with this one?

@raamdev
Copy link
Contributor

raamdev commented Jun 9, 2014

@jaswsinc Yes! That would be great. :) Feel free to assign this to yourself and add it to the Next Release milestone if you'd like to start working on this. Much appreciated!

@jaswrks jaswrks self-assigned this Jun 9, 2014
@jaswrks
Copy link
Author

jaswrks commented Jun 9, 2014

@raamdev Great! Assigned to me.

jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 12, 2014
jaswrks pushed a commit that referenced this issue Jun 12, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 12, 2014
jaswrks pushed a commit that referenced this issue Jun 12, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 12, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 12, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 12, 2014
jaswrks pushed a commit that referenced this issue Jun 12, 2014
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 13, 2014
jaswrks pushed a commit that referenced this issue Jun 13, 2014
Additional work toward achieving #130
Also resolves #206
Also resolves #95
Also resolves #193
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jun 13, 2014
jaswrks pushed a commit that referenced this issue Jun 13, 2014
@raamdev
Copy link
Contributor

raamdev commented Jun 17, 2014

Closed by PR #212

@raamdev raamdev closed this as completed Jun 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants