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.

Sign up for GitHub

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

Jump to bottom

Remove cache buster #57

Closed
paulyoung opened this issue Mar 5, 2015 · 1 comment
Closed

Remove cache buster #57

paulyoung opened this issue Mar 5, 2015 · 1 comment
Assignees
@paulyoung
Milestone
v4.0

Comments

@paulyoung
Copy link
Contributor

I was thinking about deprecating the cache buster feature in v4 since I'm sure there are more robust, dedicated tools for that which can be used in conjunction with bless.

The goal of bless has always been to split a CSS file into the optimal size based on the number of selectors.

Cache buster was something that got added for convenience along the way but it distracts from the purpose of the tool and couples bless to a different problem.

Original discussion here: #32 (comment)

There have been a lot of pull requests/issues about this, and people have opinions. I'd like to track this here.
@paulyoung paulyoung added the v4 label Mar 5, 2015
@paulyoung paulyoung added this to the v4.0 milestone Mar 5, 2015
@paulyoung paulyoung mentioned this issue Mar 5, 2015
Closed
@paulyoung paulyoung removed the v4 label Apr 26, 2015
@paulyoung paulyoung self-assigned this Apr 26, 2015
@mtscout6
Copy link
Member

The current v4 doesn't support this anymore.

@paulyoung paulyoung mentioned this issue Dec 31, 2015
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paulyoung paulyoung

Labels
None yet
Projects
None yet
Milestone
v4.0
Development

No branches or pull requests
2 participants
@paulyoung @mtscout6