Use assert.deepStrictEqual instead of deepEqual. #253
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
ghost
assigned 
googlebot
added
the
cla: yes
Codecov Report
@@ Coverage Diff @@
## master #253 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 10 10
Lines 1266 1266
=====================================
Hits 1266 1266Continue to review full report at Codecov.
|
|
Most lint issues are resolved. The only one left is:
@stephenplusplus or @kolodny, do you have any ideas on how to fix it? |
JustinBeckwith
approved these changes
Jul 24, 2018
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.
deepEqualis causing some issues in PR #247, where the linter seems to prefersdeepStrinctEqual. Also, this fixes a strange System test problem from PR #251.