-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Nested rules inside mixins #12
Comments
Ok, fixed this. I'm not allowing nested mixin.Definitions (yet), as it doesn't really make sense. But you can now call a mixin from inside another mixin, and nesting works properly. |
dhaber
pushed a commit
to dhaber/less.js
that referenced
this issue
Jan 14, 2014
Fix for some tests that were failing on my Mac
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this is an intentional restriction but the following doesn't seem to work
should output
it only works with one level of nesting, the second level is lost when you run this code in mixin.js:
You could also change this area of code to allow a mixin.Call or even a mixin.Definition inside another mixin.Definition.
The text was updated successfully, but these errors were encountered: