Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFix a small inconsistency in the .null assertion docs #423
Conversation
ehntoo
changed the title from
Fix a small bug in the .null assertion docs
to
Fix a small inconsistency in the .null assertion docs
Apr 7, 2015
This comment has been minimized.
This comment has been minimized.
|
|
added a commit
that referenced
this pull request
Apr 7, 2015
keithamus
merged commit b8807a2
into
chaijs:master
Apr 7, 2015
1 check passed
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
ehntoo
deleted the
ehntoo:patch-1
branch
Apr 8, 2015
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.
ehntoo commentedApr 7, 2015
The other assertions for undefined and the like all use '.to.not' in their examples - The slight increase in consistency is nice. :)