[expect] Fix TypeError in toBeInstanceOf on null or undefined
#6912
Conversation
This file contains hidden or 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
thymikee
approved these changes
Aug 29, 2018
packages/expect/src/matchers.js
Outdated
| )}\n` + | ||
| `Received constructor: ${RECEIVED_COLOR( | ||
| received.constructor && received.constructor.name, | ||
| received !== undefined && received !== null |
Contributor
There was a problem hiding this comment.
received != null will do both the checks
Codecov Report
@@ Coverage Diff @@
## master #6912 +/- ##
==========================================
+ Coverage 66.98% 66.98% +<.01%
==========================================
Files 250 250
Lines 10365 10360 -5
Branches 4 3 -1
==========================================
- Hits 6943 6940 -3
+ Misses 3421 3419 -2
Partials 1 1
Continue to review full report at Codecov.
|
Member
|
Pleas update the changelog as well 🙂 |
Contributor
Author
|
@SimenB Ah, thanks for the reminder! |
If using toBeInstanceOf() on an undefined or null value Jest attempts to read `undefined.constructor` which generates an unhelpful error along the lines of "TypeError: Cannot read property 'constructor' of undefined". This fixes the bug so that it's more robust and returns the normal matcher error like "Expected X, received X"
This was referenced Sep 10, 2018
ghost
mentioned this pull request
ghost
mentioned this pull request
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Summary
When using
toBeInstanceOf()on anundefinedornullvalue Jest attempts to useundefined.constructorin its error message, which throws a TypeError along the lines of "TypeError: Cannot read property 'constructor' of undefined"This makes the matcher more robust and returns a normal matcher error along the lines of "Expected X, received X"
Test plan
Also added two snapshot tests for
toBeInstanceOf()forundefinedandnulland confirmed reasonable error messages are now returned for these values.