This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Right now if you compile a bad SCSS (say, by having a wrong @include), then you get a very nicely formatted error message from the compiler, wrapped up in a CSS comment, like this
and you do get a message in the "Web Workbench Output" in Visual Studio. But it's easy to miss this as you're editing lots of stuff. It would be great if the emitted CSS were also invalid, so that it would trigger some kind of error in the browser. One we might see in the Chrome dev tools or Firebug panels. Granted, I don't know what it would have to do look "bad"... |
|