Skip to content
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

Absent line terminator after variable, recompile fails #37

Open
blackf0rk opened this issue Dec 26, 2013 · 5 comments
Open

Absent line terminator after variable, recompile fails #37

blackf0rk opened this issue Dec 26, 2013 · 5 comments
Assignees

Comments

@blackf0rk
Copy link

screen shot 2013-12-26 at 12 41 14 pm

If you forget to add a semicolon to the end of your line after a variable, the .css isn't recompiled. It seems to only fail after variables.

@darrenkopp
Copy link
Owner

Yeah, you should see an error about it in the output window in the SassyStudio pane. The error is coming from libsass and you would likely see this error with other precompilers (ruby sass gem, compass gem) as well. I'll add some error integration into the extension so that you get some red squigglies there, but I don't know if there's anything else I can do.

If the problem is mainly that you don't notice when this happens, there's an option that will replace the css file with the exception so that you can easily notice that there was a problem as everything will lose it's styling.

@blackf0rk
Copy link
Author

@darrenkopp I see the error in the output window now, thanks. I also found that if you reference a variable that doesn't exists, the css doesn't compile either. I think it would be helpful to have syntax highlighting under elements that would cause a compilation to fail.

I can't speak for other developers, but I don't keep my output window open, so it would be helpful if there was, at the very least, some sort of warning/alert if the css fails to compile. As soon as I would save the .scss file I would get that warning, and I would know that whatever it was I was working on last is wrong; as opposed to working with the file, saving, thinking nothing is wrong and then 30 lines later realize it's not compiling.

@darrenkopp
Copy link
Owner

Yeah I haven't been able to figure out how to get the output window to pop open when I'm telling it to do that, but for now I'd definitely tick the 'Replace .css with exception' option in Tools > Options and Setings > Sassy Studio > General. This will make exceptions far more apparent when they happen in the meantime.

@blackf0rk
Copy link
Author

That's good enough for me, thanks! 👍

@darrenkopp
Copy link
Owner

Cool, I'll revisit how close I am for error / warning integration. When that is done, I'll close this issue with that as the resolution.

@ghost ghost assigned darrenkopp Dec 29, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants