Skip to content
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

Merged
merged 48 commits into from
May 7, 2019
Merged

Merge master into feature.use #1389

merged 48 commits into from
May 7, 2019

Conversation

nex3
Copy link
Contributor

@nex3 nex3 commented May 6, 2019

[skip dart-sass]

nex3 and others added 30 commits March 15, 2019 15:04
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.
These are getting in the way of removing Ruby Sass testing.

Closes #1305
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
mgreter and others added 18 commits April 12, 2019 03:40
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.
Add specs for attribute selectors with modifiers
Copy link

@srawlins srawlins left a 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...

@nex3
Copy link
Contributor Author

nex3 commented May 7, 2019

Because this is merging in #1372, which deleted the very large spec/output_styles directory.

@glebm
Copy link
Contributor

glebm commented May 7, 2019

Perhaps this should be a rebase instead of a merge?

@nex3
Copy link
Contributor Author

nex3 commented May 7, 2019

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.

Copy link

@srawlins srawlins left a 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 😛

@nex3 nex3 merged commit 987a66e into feature.use May 7, 2019
@nex3 nex3 deleted the merge-master branch May 7, 2019 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants