Fix toInclude to use deepEqual
#44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kentor
force-pushed
the
fix-to-include-should-use-deep-equals
branch
from
56b597b to
999fe2c
Compare
as per the docs. This behavior is consistent with Jasmine's `toContain`.
kentor
force-pushed
the
fix-to-include-should-use-deep-equals
branch
from
999fe2c to
46ee2de
Compare
kentor
changed the title
toInclude to use deepEqual
|
LGTM |
mjackson
added a commit
that referenced
this pull request
Nov 2, 2015
Fix `toInclude` to use `deepEqual`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.