fix(deps): update dependency chai to version .x 🌟 #4227
Closed
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.
This PR contains the following updates:
1.10.0
->3.5.0
Release Notes
chaijs/chai
v3.5.0
Compare Source
For
assert
fans: you now haveassert.includeDeepMembers()
which matchesexpect().to.include.deep.members()
and.should.include.deep.members()
!This release also includes a variety of small bugfixes and documentation fixes. Most notably, we are now governed by a Code Of Conduct - which gives Chai contributors (including those who files issues, work on code, or documentation, or even just hang out on our Slack & Gitter channels) safety from harassment and discrimination.
Full changes below:
Community Contributions
assert.includeDeepMembers()
. By @qbolecDocumentation fixes
v3.4.1
Compare Source
This is a small documentation bug fix release - it just fixes a couple of issues with the documentation.
Community Contributions
Documentation fixes
.throws()
example. By @Pklongv3.4.0
Compare Source
This release improves some confusing error messages, and adds some new assertions. Key points:
expect(1).oneOf([1,2,3])
- for asserting that a given value is one of a set..include()
(and variants) will now give better error messages for bad object types. Beforeexpect(undefined).to.include(1)
would say "expected undefined to include 1", now says "object tested must be an array, an object, or a string but undefined given".throw()
(and variants) can now better determine the Error types, for exampleexpect(foo).to.throw(node_assert.AssertionError)
now works..closeTo
is now aliased as.approximately
.empty
changes from 3.3.0 have been reverted, as they caused breaking changes to arrays which manually set keys.Community Contributions
Code Features & Fixes
expect(inList).to.be.oneOf
assertion. By @DroogansDocumentation fixes
new Error
type gets detected by thea
/an
matcher. By @jurko-gospodneticv3.3.0
Compare Source
This release adds some new assertions and fixes some quite important, long standing bugs. Here are the cliff notes:
frozen
,sealed
orextensible
assertions to test primitives (e.g.expect(1).to.be.frozen
), you may have noticed that in older browsers (ES5) these fail, and in new ones (ES6) they pass. They have now been fixed to consistently passassert
interface has been given the following new methods, to align better with other interfaces:,assert.isAtMost
,assert.isAtLeast
,assert.isNotTrue
,assert.isNotFalse
.Community Contributions
Code Features & Fixes
assert.isNotTrue
andassert.isNotFalse
.By @cezarykluczynski
frozen
/extensible
/sealed
assertions behave the same in ES6 and ES5 environments.By @astorije
.empty
assertion.By @Daveloper87
assert.isAtMost
andassert.isAtLeast
.By @wraithan
By @kpdecker
Documentation fixes
isBelow
,isAbove
,isTrue
).By @cezarykluczynski
v3.2.0
Compare Source
This release fixes a bug with the previous additions in
3.1.0
.assert.frozen
/expect().to.be.frozen
/.should.be.frozen
all accidentally calledObject.isSealed()
instead. Now they correctly callObject.isFrozen()
.If you're using these features, please upgrade immediately.
It also adds aliases for a lot of
assert
methods:Community Contributions
Code Features & Fixes
By @keithamus
By @couchand
getProperties()
utilityBy @jluchiji
By @jluchiji
By @astorije
By @astorije
v3.1.0
Compare Source
This release adds assertions for extensibility/freezing/sealing on objects:
It also adds assertions for checking if a number is NaN:
Community Contributions
Code Features & Fixes
By @bradcypert
By @matthewlucock
version
property from bower.json.By @kkirsche
v3.0.0
Compare Source
This release contains some small breaking changes. Most people are unlikely to
notice them - but here are the breaking changes:
you're using RequireJS with Chai, you might notice a change (chai used to
be a global, now it won't be - instead you'll have to
require
it)..has.property('foo', undefined)
will now specifically test to make surethat the value
'foo'
is actually undefined - before it simply tested thatthe key existed (but could have a value).
.to.be.a('type')
has changed to support more types, including ES6 typessuch as
'promise'
,'symbol'
,'float32array'
etc, this also means usingES6's
Symbol.toStringTag
affects the behaviour.to.be.a()
. In addition tothis, Errors have the type of
'error'
.assert.ifError()
now follows Node'sassert.ifError()
behaviour - in otherwords, if the first argument is truthy, it'll throw it.
Community Contributions
Code Features & Fixes
assert.ifError()
behaves like Node.js: it throws if the first argument is present.By @cjqed
^1.0.1
By @keithamus (special thanks to @simonzack for his work on assertion-error)
By @Charminbear
.matches()
as alias for.match()
.By @thejameskyle
By @csnover
.property('foo', undefined)
now actually checks to see ifobj.foo === undefined
(before it did not).By @onefifth
By @keithamus
Documentation fixes
.assert()
By @astorije
By @keithamus
.keys()
By @astorije
.length(n)
from the docs - use.lengthOf(n)
instead.By @valscion
.length(n)
examples to.lengthOf(n)
instead.By @keithamus
assert.notInclude
docsBy @BinaryMuse
v2.3.0
Compare Source
==================
make test-firefox
ownPropertyDescriptor
assertion.v2.2.0
Compare Source
==================
.deep
flag..deep
flag..deep.property
v2.1.2
Compare Source
==================
git summary
in READMEv2.1.1
Compare Source
==================
v2.1.0
Compare Source
==================
v2.0.0
Compare Source
==================
.keys(object)
by
cleanup.by
for #333change
to work w/ non-number values + testschange
(#330)change
,increase
,decrease
assertions (#330)change
,increase
,decrease
change
,increase
,decrease
undefined
value pass property assertionRenovate configuration
📅 Schedule: "before 3am on the first day of the month" in timezone America/New_York.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!
".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.