-
Notifications
You must be signed in to change notification settings - Fork 462
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
libsass does not give errors for missing imported base class in @extend #871
Comments
+1 encountered the same issue |
+1, using Sass 3.4, seeing same issue |
Thanks for the reports. I'll try to get this into our next release. |
This one is also trickier than expected. @xzyfer you added the 3.2 Milestone for this, so do you have an idea how to fix this? I was able to tackle the missing error when extending across media queries, but this one seems more difficult, since extend seems to be run twice, which makes my check in the WIP branch fail on the second run. Otherwise I don't think I can fix this for 3.2! |
@mgreter the way to handle this is by setting metadata on the extends in the cssize visitor. This isn't a difficult fix to the looks of it, I'm just not sure if I'll the time before 3.2.0. I'm pretty much out of action this month. You can see the Ruby sass implementation in the cssize visitor and the actual error in the extend visitor. IMO this is non-critical and can be delayed to 3.3 if it's the only 3.2 blocker. |
Rescoping to 3.3, since it is a non trivial refactoring and we consider this issue a minor one, because it only happens with "invalid" input. As a drop-in replacement, libsass does not break, since ruby sass would not create any output anyway! We still consider it a bug, but will not have a fix in 3.2! |
Rescoped to 3.4 since this doesn't prevent people migrating to LibSass from Ruby Sass. |
This PR activates specs for sass/libsass#871
Given the following code
ruby-sass gives the following error:
While libsass (by way of node-sass) gives:
This was performed using node-sass (2.0.0-beta). I think libsass should also throw an error instead of proceeding with the compilation. My apologies if I am seeing this incorrectly.
The text was updated successfully, but these errors were encountered: