-
Notifications
You must be signed in to change notification settings - Fork 113
Sass Scanner #93
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
Sass has been added. |
Can I refuse to write a SCSS scanner? The http://thesassway.com/articles/sass-vs-scss-which-syntax-is-better discussion is really the pinnacle of meaningful-whitespace-phobia :( |
Hah, well I suppose you can, but I think SCSS is a little more popular than the older whitespace SASS format. |
True. But the Sass syntax is by no means "old", it's just too modern for design folks. Should be easier to parse though :-) |
I'm with you on preferring SASS. Especially the lack of semicolons. Though shouldn't SCSS be similar to CSS to parse? |
Yes, it's essentially CSS plus the new Sass tokens. I'm trying to re-use as much as possible, but with CodeRay's method-based scanners that still means a lot of duplication. |
Creating a new ticket for the SCSS scanner. Thank you for your support, @nathany :) |
Syntactically Awesome Style Sheets come in two formats: the whitespace significant original (sass) and the popular CSS-derived alternative (scss). This may require 2 separate scanners, though they share the same keywords, etc.
Reference:
There are a number of SASS mixin libraries for sample code:
The text was updated successfully, but these errors were encountered: