-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Scoping of mixin unlocked from namespaced mixin does not work properly #2039
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If I'm not mistaken the (1) error is actually expected since it occurs when the
|
And (2) is just one more example for #1316. |
EDIT: ignore this comment, contains mistakes. 2.) You are right. I forgot about that one. 1.) Mixin should see callers variables. I can not find related discussion now, but I'm sure about it. I will try to find it tomorrow. That being said, this issue has nothing to do with unlocking. It seems like .mixin() {
property: @variable;
}
#usePlace {
.mixin();
@variable: in-caller;
} compiles into: #usePlace {
property: in-caller;
} On the other hand, this fails: .mixin {
property: @variable;
}
#usePlace {
.mixin();
@variable: in-caller;
} Error:
Do you agree? If yes I will close this issue and open new one for |
Blah, ignore previous comment. Closing issue because 1.) works as expected and 2.) is duplicated. |
This is probably related to #2038
1.) Mixin unlocked from namespaced mixin does not see callers variables.
Less:
actual output:
expected output:
2.) I defined a detached ruleset inside a namespaced mixin. The ruleset is unable to see variables defined in its outer namespace (the #2038 is the same except with detached rulesets).
actual output:
expected output:
I use node.js with lessc 1.7.0 (LESS Compiler) [JavaScript]
The text was updated successfully, but these errors were encountered: