Update sass-true to the latest version 🚀 #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 3.0.0 of sass-true just got published.
The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of sass-true.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
True 3.0!(copied from 3-beta release notes…)
describe
andit
mixins,as alias for
test-module
andtest
respectively.$inspect
argument toassert-equal
andassert-unequal
mixins,for comparing
inspect($assert) == inspect($expected)
instead of
$assert == $expected
.This helps with several of the equality edge-cases listed below
(rounding and units).
in favor of allowing Sass to determine the best comparisons.
There are a few edge-cases to be aware of:
manipulated numbers and colors are compared without rounding,
so
1/3 != 0.333333
andlighten(#246, 15%) != #356a9f
.Use the
$inspect
argument to compare rounded output values.unitless numbers are considered comparable to all units,
so
1 == 1x
wherex
represents any unit.Use the
$inspect
argument to compare output values with units.so
(one two three) != (one, two, three)
.This can be particularly confusing for single-item lists,
which still have a delimiter assigned,
even though it is not used.
Commits
The new version differs by 65 commits.
4c59152
Release v3.0.0
c5f0de5
add contributor
e9460b9
yarn.lock
00f5ded
Merge pull request #109 from oddbird/greenkeeper/chalk-2.0.0
40d7647
chore(package): update lockfile
82ff544
chore(package): update chalk to version 2.0.0
4ae9bb0
Add remotes-fix to npm script
6853dd3
Update docs
3f22624
Merge pull request #107 from oddbird/tilde-docs
ce84b7e
Compile doc changes
074f1d5
Add docs on tilde imports
7e39f3e
Merge pull request #106 from oddbird/greenkeeper/initial
b9c2b43
chore(package): update dependencies
0458b62
docs(readme): add Greenkeeper badge
8233bda
update yarn.lock
There are 65 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴