These are chat archives for less/less.js

17th
Dec 2015
Matthew Dean
@matthew-dean
Dec 17 2015 22:50
@zephraph Not sure what you mean. What's the difference?
Zephraph
@zephraph
Dec 17 2015 23:22
This message was deleted
Eh, nevermind.
Matthew Dean
@matthew-dean
Dec 17 2015 23:23
Yeah, but.... explain why you would use that
I mean either form.
Matthew Dean
@matthew-dean
Dec 17 2015 23:23
Although... I guess I've used the latter. But it's more clear what it's scoped to.
Like I would expect @import (scoped) to be scoped to the current block. Which it already is
Zephraph
@zephraph
Dec 17 2015 23:24
Essentially to import things without having the variables conflict.
Ah, yeah, I suppose...
Matthew Dean
@matthew-dean
Dec 17 2015 23:24
Yeah.
Zephraph
@zephraph
Dec 17 2015 23:25
I solved the problem in a different way.
Matthew Dean
@matthew-dean
Dec 17 2015 23:25
@import (isolated) ?
Oh good
Zephraph
@zephraph
Dec 17 2015 23:25
heh, something like that would work, yeah.
I just solved it in the build instead of leaving it to less to handle.
Matthew Dean
@matthew-dean
Dec 17 2015 23:26
One way I've solved that is that the "root" .less file for the library imports the real root using & { }
so that an end user can import normally, and there's no conflict with internal vars
Zephraph
@zephraph
Dec 17 2015 23:27
Ahhh, I see.