LESS: Using variables in @import statements breaks Codekits awareness of file imports.

[pedrocorreia]

foobar.less:

@path: "../stuff/";
@import "@{path}_foo.less"
@import "@{path}_bar.less"
@import "@{path}_baz.less"

When using variables as part of import paths, codekit no longer is aware of the imports.

In the exemple, compilation of foobar.less is done correctly, but if any of the imported files is changed, Codekit will try to compile it independently.

[bdkjones]

Not too much I can do here. CodeKit is not aware of variables in Less, like the Less compiler is as it runs. That is, the app simply scans for @import statements; it does not have the full token table to work with --- that is created by the less compiler when it runs.

Sent from my iPhone

On Jul 9, 2013, at 6:35, Pedro Correia notifications@github.com wrote:

foobar.less:

@path: "../stuff/"; @import "@{path}_foo.less" @import "@{path}_bar.less" @import "@{path}_baz.less" When using variables as part of import paths, codekit no longer is aware of the imports.

In the exemple, compilation of foobar.less is done correctly, but if any of the imported files is changed, Codekit will try to compile it independently.

— Reply to this email directly or view it on GitHub.

[pedrocorreia]

Ok, just thought it would be worth mentioning.