Fixed handlebar spam messages from code coverage report generation #980
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
Codecov Report
@@ Coverage Diff @@
## master #980 +/- ##
=======================================
Coverage 96.24% 96.24%
=======================================
Files 93 93
Lines 3599 3599
Branches 728 728
=======================================
Hits 3464 3464
Misses 79 79
Partials 56 56
Continue to review full report at Codecov.
|
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.
When running
$ cd raiden-dapp $ npm run test:unitwe encounter the same spam messages from handlebars like in:
To fix it, I had to remove
node_modulesandpackage-lock.jsonand runnpm iagain.The new
package-lock.jsonseems to have pinned a newer version ofistanbul-reportsthat has a fix for this issue.