-
Notifications
You must be signed in to change notification settings - Fork 465
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
Support Sass 3.5 #927
Support Sass 3.5 #927
Conversation
In Sass 3.5, `node.value` returns an Array instead of a String. This could mean that we could expect multiple strings. With this PR, SCSS-Lint will check the first string returned. Also, Sass 3.5.3 fixes a couple of issues which previously need a monkey patch in SCSS-Lint. This PR uses '~> 3.5.3' as the minimum required version of Sass Fix: sds#877 Ref: sass/sass#1799, sass/sass#2394
Sass 3.4.20 contains a fix that allows SCSSLint to remove its `add_line_numbers_to_args` method Ref: sass/sass@d6ea4c6
👏 🙇 |
I want to submit a new PR that:
What do you think? |
Hey @tagliala, thanks for offering to move us forward on some of these issues.
Thanks! |
Hi,
|
Thanks for linking to the diff for If you find yourself down the road having an issue with the coverage information reported by SimpleCov, then I would be open to merging |
RuboCop released a new version, but it has a lot of false positives, so I will keep waiting. Moreover, Sass 3.5.4 has an issue (fixed in the stable branch) and a lot of tests with this gem fail sass/sass#2423, so I will wait for a new release of Sass, too |
This is not the PR we deserve, but it's the one we need right now.
Sass 3.5 is supported, custom properties aren't: all specs are green (included the new one which deals with custom properties), and it does not fail against Bootstrap v4
Also:
Fix #877