You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project I store the test files (*.test.ts) side-by-side with the files to be tested (*.ts). Naturally, the test files don't have any coverage associated with them.
However, when opening them, coverage-gutters tries to find the best match and selects a completely unrelated coverage to display:
I'd prefer if for such low exactness score no coverage would be displayed instead (or made optional), because now the test files are riddled with a bunch of red bars in weird locations:
The text was updated successfully, but these errors were encountered:
@AlCalzone Thanks for the issue, I am looking into this issue this weekend. I am planning to either make a feature to not render coverage if less then a certain score or remove the scoring feature and go back to relative path determination for coverage showing.
In my project I store the test files (*.test.ts) side-by-side with the files to be tested (*.ts). Naturally, the test files don't have any coverage associated with them.
However, when opening them, coverage-gutters tries to find the best match and selects a completely unrelated coverage to display:
I'd prefer if for such low exactness score no coverage would be displayed instead (or made optional), because now the test files are riddled with a bunch of red bars in weird locations:
The text was updated successfully, but these errors were encountered: