-
Notifications
You must be signed in to change notification settings - Fork 89
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
Merge master into feature.use #1389
Conversation
Add specs for CR, CR LF, and FF line endings
1. Changes `folder` to `dir.to_s` (`folder` no longer exists). 2. Changes `passing.any?` to `!passing.empty?`, as `any?` has pitfalls: Took me a few minutes to debug when I tried with `input_path` that was returning `nil` (`[nil].any? #=> false`).
These 2 files are used to test UTF8 paths directly with sassc executable, requiring a real directory. This special handling is required to test fully on Windows (Ruby wrapper can mask bugs), see sass/libsass#1774.
Follow-up to #1370
Drop support for Ruby Sass
These are getting in the way of removing Ruby Sass testing. Closes #1305
This reverts commit 368cfed.
Run specs from within the spec directory This means all reported paths will be relative, which makes it much easier to move specs without having to regenerate expected error messages.
This also deletes all directories with an :end_version:.
Drop support for multiple language versions
Add todo spec test for libsass issue 2863
This PR activates specs for sass/libsass#2863
Activate specs for issue 2863
Add tests for `quote`
I've tried to capture the best practices I've come up with while writing tests in the HRX format, mixed with best practices from other testing traditions and a few rules that mostly serve to just establish a consistent style.
Follow-up to #1380
Add specs for attribute selectors with modifiers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi level question: why is it 99% deleted? Looks like a lot of the specs are deleted...
Because this is merging in #1372, which deleted the very large |
Perhaps this should be a rebase instead of a merge? |
Rebases of many commits tend to make it harder to resolve merge conflicts, and provide a less accurate view of the evolution of a branch over time. Also you can't do pull requests for them, which means you don't get CI verification of their validity before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok sounds good; just as long as -259,830
is expected 😛
[skip dart-sass]