Fix #1638: resetHistory for props #1677
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
The test implementation was using objects with `resetHistory` methods. However, the only valid things to have in the `fakes` collection are spies (functions) or property descriptors (objects with spies), which have `resetHistory` methods.
mantoni
approved these changes
Jan 26, 2018
|
This has been published as |
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.
This PR is a fix for #1638.
The first commit is a fix for a poorly constructed test. Reviewers: is the commit message adequate to describe what the issue was?
How to verify - mandatory
npm installnpm testChecklist for author
npm run lintpasses