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
3.5.3 regression: importing .css
files fails instead of warning (as the release notes indicate)
#2636
Comments
I think this can be closed, this is exactly what was expected by #1963. Personally, I think it should have been depreciated via a warning first and caused a minor release rather than patch, but it's too late now. |
Sorry this was an unintended breaking change for this patch release. My preference is to roll forward with change and update the release notes. You'll need to use the Note: doing so will result in deprecation warning for |
I'm very confused by the depreciation, nowhere seems clear:
vs.
Will the depreciation warning be removed in 3.6.0 and Personally, I would say it would be a big step back for libsass to stop supporting css imports, this will either mean:
I don't use ruby, I'm not going to and I couldn't care less what it does and doesn't do. Please can we keep |
Apologies for not being clear. The release notes have since been updated to hopefully be more clear.
Firstly this isn't us vs Ruby. Sass is a language with a specification like any other. The Ruby implementation is the source of truth for the Sass language specification. Raw CSS imports is a feature that violates the Sass language spec, and should never have been in LibSass. It must be removed. Since people have become so dependant on it we need to remove it in a responsible way. As such we're making it an opt-in behaviour via The deprecation warning was added in 3.5.x because there aren't sufficient hooks in LibSass for an implementor to performantly produces the correct deprecation warning. It is the deprecation warning that will be removed in 3.6. This is where we would expect implementors to bump their majors should the desire to maintain spec compliance. |
Thanks for clarifying. I've just read the module proposal for sass 4 and it looks great. |
See also sass/node-sass#2362 for dealing with this on the node-sass end. |
Originally reported here: sass/libsass-python#245
input.scss
cssfile.css
libsass 3.5.2 (via libsass-python)
libsass 3.5.3 (via libsass-python)
I expect the warning noted in the release notes
The text was updated successfully, but these errors were encountered: