You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files with a CSS extension are processed but imports ending in .css are not. Is this made for performance?
There is no such restriction in the Ruby version and it will be great if it at least can be made optional. I prefer using .css instead of .less because text editors recognize it by default and colorize the LESS syntax fairly well.
I traced the problem to the following line in the tree.Import function:
this.css = /css$/.test(this.path);
The text was updated successfully, but these errors were encountered:
Hmm, yea the reason is to allow a little more flexibility, so you can import actual css files if needed.
I could add an option to the parser, or have two kinds of import directives, the standard @import would just pass through untouched, and if you want it to be parsed, you'd use something like @include.
I was actually grateful that .css files weren't parsed because it was the only way I could include a @-webkit-keyframes definition. But I do like the idea of having @import and @include where the latter is untouched.
Files with a CSS extension are processed but imports ending in .css are not. Is this made for performance?
There is no such restriction in the Ruby version and it will be great if it at least can be made optional. I prefer using .css instead of .less because text editors recognize it by default and colorize the LESS syntax fairly well.
I traced the problem to the following line in the tree.Import function:
this.css = /css$/.test(this.path);
The text was updated successfully, but these errors were encountered: