Closed FagnerMartinsBrack closed 11 years ago
This is a problem which is unfortunately difficult to solve in an IDE. Indeed, one cannot check the file "wells.less" by itself, as it may be correct or not, depending on which file it is included. You could have another main2.less somewhere in your project (or somewhere else) that imports wells.less without importing mixins.less.
Requiring explicit imports sounds like a good programming practice. I think also this is one of the reason for the change of the semantics of the import statements ("import once") in the LESS compiler.
But if I use the import somewhere my code will be repeatedly generated. Is there any solution for this? It is completely unusable without such feature. Maybe create an option to disable any import verification.
You could use Intellij IDEA as example for this implementation. I do not use it, but ppl said they have a good less syntax highlight and validation.
I am really sad for the lack of support Eclipse itself has with less language. I hope it changes in the future =(
This is really important. I have no idea of workaround using the current implementation of less and the plugin =/
The thing is the following also happens in the same situation: `Couldn't resolve reference to VariableCrossReference '@headings-color'. type.less
Can you send me a link to the code of the project you are working on, so that I can see if I have a solution for it?
Ok I messed around and solved it with @import-once
in all files. But the thing is I can't use a single import in a main file. That's a problem, but at least is not a blocker one.
You can now disable error messages on undefined mixins and variables thanks to #135.
Thanks man, appreciated that ;)
main.less
mixins.less:
wells.less:
outputs (when compiling bootstrap.less):
An error is thrown into the line of the
well.less
file and should notThe mixin '.box-shadow' is undefined in this context.
. I can arrange a project for you if you are not able to reproduce this.