This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a bunch of .less files which are used as includes, and don't generate any .css files of their own. They are typically references from my main .less file like so; @include "mixins.less"; @include "fonts.less"; etc When editing mixins.less in VS, I can save it fine and WW knows to recompile the main less file automatically - plus it recognises variables defined in other .less files (but not directly referenced). Can this somehow be mimicked from the command line compilation? If I compile main-nav.less via wwcmd, it throws errors about undefined vairables. I'm guessing VS knows which other less files are in the project, so it can somehow reference them at the same time. Can this be done via wwcmd? Thanks, Phil |
|
|
|
|
Yes the Visual Studio extension has a bit more awareness about other files in the solution. The command line tool is intended to operate over single files and not deal with relationships. How does main-nav.less reference those variables which are undefined normally?
|
|
|
|
|
Normally referencing variables like @border in main-nav.less just works - even though there is no explicit reference to their source - e.g. @import "Style.less". I guess WW just knows where to find them. Perhaps this could be fixed by explicitly referencing the .less file that the variables are contained in, but in my case, that would require breaking out the variables from other LESS code so that the CSS rules aren't imported twice. That's probably a better design anyway. Thanks for the clarification. Phil |
|
|
|
|
Another question related to this - is it possible to produce source maps with wwcmd? (like WW can in VS) |
|
|
|
|
Not yet, but this will be coming to a nightly very soon :) Ive added a /map option to the recent builds which supports this. Currently we are updating things in general around Sass 3.3 coming out and we will be shortly putting out a new update (also version 3.3) which will include this change :)
|
|
|
|
|
Awesome - thanks. |
|
|
|
