Using @import with relative path and dotless.Core.Less.Parse

In our system we have a scenario where we need to use…

dotless.Core.Less.Parse(LESSInputAsString, config)

The problem here is that if LESSInputAsString contains a @import statement we need to force dotLESS to look for these imports relative to a specific folder.

Each “template” in our system generates it’s own supporting files directory and this is where any additional .less files would be kept. We need to point dotLESS to this folder and have it look there (or at least start there for relative paths) when using @import

[lukeapage]

Yes, I think it should be configurable, so keep this bug open.

If all your less files are stored in the database you could create your own virtual file system accessor like the unit tests do - then less wouldn’t have to access the file system at all.

[rnorbauer]

Might it be possible to get some example syntax for how one would use this CurrentDirectory configuration option? I have no problem sub-classing and overriding the method, but I’m not sure what to do with my resulting IImporter object so I eventually build up to an object with a Parse method that gives me back a string. :S