-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for per-each file coverage check #611
Comments
seems like this can be relatively simple to implement by enhancing NYC::checkCoverage Line 444 in 213206f
|
I think this is addressed in #591. Feel free to test it out by installing:
|
Looks like exactly what I was looking for. Thanks @JaKXz for pointing this out! |
@ciekawy this feature is now landed 👍 |
Is there a way to do it both per file and globally like it was done previously in Istanbul? Can this be set in an |
I see this was outlined here - #468 - but doesn't seem possible yet. |
Please use the template provided below, when reporting bugs:
Expected Behavior
support to provide and require thresholds per-each file like in
gotwarlost/istanbul#30
Observed Behavior
not possible to define per-each file coverage checks
Bonus Points! Code (or Repository) that Reproduces Issue
Forensic Information
I believe this is just not supported yet so skipping following sections, can add this info anytime
Operating System: the operating system you observed the issue on.
Environment Information: information about your project's environment, see instructions below:
sh -c 'node --version; npm --version; npm ls' > output.txt
The text was updated successfully, but these errors were encountered: