Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New rule: no istanbul ignore without reason
See original GitHub issueWhen using the coverageThreshold option of jest you sometimes you have to add /* istanbul ignore next */ comments in order for your coverage to much the threshold.
Often people will add this comment with no reason of why the code is not covered (examples: covered in e2e, can’t be covered, will be covered later…).
I think the reason why it’s uncovered should be documented so other developers will know how to handle this code in the future, and that’s why this rule would be useful.
What do you think? Is it related enough to jest to be here?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We should link to the recently released
eslint-plugin-istanbulfrom our READMEAgreed, would be nice to get this in. Wanna provide a PR? 😀 Ideally this would be in some sort of
eslint-plugin-istanbul, but as far as I can tell that doesn’t exist. Istanbul backs all of JS code coverage (vianycorc8(as well as Jest, of course)), and such a rule seems useful for all