-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
CSS Output optimization #3029
Comments
We could, but why would we? From your example it's not even clear if you're looking for a CSS output optimization (i.e. a feature that eliminates "duplicated" properties where necessary - in that case all you need is a descent CSS minifier, e.g. Or if you're proposing a mixin overriding feature, which is another story, then the further discussion badly needs a concrete use-case example(s). Start with #1372, #2532 and other related tickets referenced there to collect some background. |
Not closing yet, but it's either "Not a Less scope (use a minifier)" or a duplicate of #2532. |
When we use 'css minifiers', all of the css files minified! but if we want it just for some parts, we must have a feature to do this! |
You can always apply |
Can we add a new feature to mixin for supporting this state?
.test() { color: white; } .test() { color: red; } body { .test() }
Compiled to:
a { color: white; color: red; }
But desired compile is:
a { color: red; }
The text was updated successfully, but these errors were encountered: