How to report coverage only on files marked with "// @flow"? #85
Comments
|
@moroshko not yet, but it is definitely a good idea. It is definitely possible to introduce this feature by using the |
dmnd
added a commit
to dmnd/flow-coverage-report
that referenced
this issue
Jul 10, 2017
When calculating coverage for a project, I don't care about coverage in files that don't have the `@flow` pragma. While it's nice that Flow infers types anyway, since it's never going to report an error it doesn't help me at all and is potentially misleading. For example, my project is 75% covered with master, but only 34% covered with this change. This PR changes flow-coverage-report to ignore coverage in unannotated files. This could be considered a breaking change or a bugfix - I'm not sure. You might consider making this a configuration option. Resolves rpl#85
This was referenced Feb 27, 2018
feat: Implement a new --strict-coverage option to enforce a more strict coverage reporting mode
#141
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started to add flow annotations to my project by adding
// @flowto certain files.I would like to make sure that those files are passing a certain flow coverage threshold.
At the moment, it looks like the files included in the coverage report are based on
-i(and-x).This causing the covered percent to be very low.
Is it possible to report coverage only on files marked with
// @flow?The text was updated successfully, but these errors were encountered: