-
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
3.4 support blockers! #629
Comments
IMHO it's work creating issues for each of these and assigning them to a 3.4 milestone as per our roadmap. As is stands this issue doesn't feel actionable or approachable. Thoughts? |
Welcome back @hcatlin! Thoughts on my previous comment? |
The "weird issue with unquote(0xf00)" seems to have been fixed in ruby sass! |
I've created #772 which I'll ship in 3.1.next. It addresses |
@hcatlin I'd say it's work updating all todo specs on master so we don't end up patching against 3.3 functionality. I don't see any harm if they're already being skipped. |
Sorry for not breaking this up. I'm a lazy, lazy developer. I'm updating the specs to match 3.4.9 |
Is this still accurate? There is only one blocker from 3.4 compatibility? |
This is correct as of the current master with regards to major language features. If you want a more specific list of issues look at the github issues. |
All of the supplied specs are passing as of current master. All outstanding failing specs have been converted to issues. There is now a https://github.com/sass/libsass/issues?q=is%3Aopen+is%3Aissue+label%3A%22Bug+-+Confirmed%22 |
Hey yo! Here is a mega ticket. I just went through all the specs over at sass-spec and made a new branch called "threefour" that is 100% s3.4 compatible in all tests. This is basically the primary hitlist for 3.2 development.
Here are the things I noticed breaking, and the tests that cover them.
@at-root
supportThe text was updated successfully, but these errors were encountered: