-
Notifications
You must be signed in to change notification settings - Fork 3.4k
issue with variable scope in namespaces #719
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
Hi, |
which part shouldn't work? which part doesn't work in the correct way? how is it connected to the theory that "namespaces are still rules"? How your comments lead closer or even connected to the solution or at least the explanation of the issue? |
My problem is, this one is the 7th comment and i (and people who also interest how scopes work in deep) didn't get any closer to the solution. The original scope issue exposed in this ticket as a reminder, is: why the compilation fails if i remove the comment in the 2nd line, while the .rect() mixin can flawlessly see the I'm waiting for some people who can see the problem exposed. |
It's because |
Thanks souldreamer, that's clear and makes sense. actually i wanted to customize semantic.gs a bit to be able to define more than one grid system (embedding the gs lib into a namespace with all its vars and mixins, @gridsystem-width would be the Thinking over your explanation i understand that the above example is not an issue and have to work around some other way. I close the issue. |
Hello,
please check the following code compiled flawlessly by less.js:
The issue: if i remove the comment before the
@w : @size;
the compilation fails.Is there a particular reason why? Why the mixin body can see the
@size
variable and the variable defining rule can't, in the #lib namespace?Regards, nlac
The text was updated successfully, but these errors were encountered: