Import fails when filename is "css" (less thinks thats the extension)

[felixsanz]

For example, parsing this:

@import "syntax/c";
@import "syntax/css";
@import "syntax/go";

CSS import is ignored and the line appears in the CSS result as @import "syntax/css";. (It's not resolved the import)

This is fixed changing it to @import "syntax/css.less";.

---

Documentation here: http://lesscss.org/features/#import-directives-feature-file-extensions

Says:

@import statements may be treated differently by Less depending on the file extension:

If the file has a .css extension it will be treated as CSS and the @import statement left as-is (see the inline option below).
If it has any other extension it will be treated as Less and imported.
If it does not have an extension, .less will be appended and it will be included as a imported Less file.

So it's clearly an issue failing to identify the extension for syntax/css (which is syntax/css.less)

[seven-phases-max]

Yes, it seems to be a regression of one of early 2.0.x branches (before 2.x it worked as you expect).

[seven-phases-max]

If I'm not mistaken the change was made to support imports like:

@import "https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700";

that otherwise would result in a broken (less) import (obviously since there's no css extension in that url).
So the fix is easy but requires documenting the breaking cases. I.e. all such urls to appear as:

@import (css) "https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700";

[seven-phases-max]

So per above observation adding "NeedsDecision" label, as the trick is that it's not hard to guess that count of such "font" urls used out there vastly outnumbers the use-case of the initial post and then it's actually questionable if it's better to keep current behaviour and change the docs instead.

[matthew-dean]

Support for this very thing was added to 3.x. #2955

It could probably get merged into a 2.x release if important.

[seven-phases-max]

So I'm closing as fixed in #2955.