vscode-lcov
vscode-lcov copied to clipboard
Screenshots:  when clicking on one section:  Flutter version: `[✓] Flutter (Channel stable, v1.0.0, on Linux, locale it_IT.UTF-8) `Flutter lcov generated with; `flutter test --coverage` VSCode version: `1.30.1 x64...
I could get open the "Show Coverage Report", it shows up fine within VSCode. When I click on any individual file/link, that particular file(or report for that particular file) does...
First of all, this extension is awesome! Request for changing the two level LCOV Menu into a single level actions, like: > LCOV: Toggle decorations > LCOV: Show coverage report
When I look at the extension description on github, vscode marketplace or inside vscode. The images linked to in the README are broken. I see that they reference "https://cloud.githubusercontent.com/assets/5047891/18036349/9101c648-6d68-11e6-9502-4ed14e03f51e.gif" :...
Currently the [README.md](https://github.com/alexandrudima/vscode-lcov/blob/d54547de5813c66baf22cbe570ce14ebfaa90434/README.md#coverage-report) still says to use the `Ctrl+T` or the `Cmd+T` keybinding. This was very confusing the first time I used this extension as this keybinding has since been...
The code coverage plugin I use in PhpStorm shows coverage numbers next to each directory and file name in the file explorer. It's one of my favorite features of the...
My code coverage setup generates files called lcovonly instead of lcov.info (and it's not easily changeable). I had to edit dataBank.js to specify `**/lcov*` instead of `**/*.info` to get things...
With the dark VSCode theme, the coverage report is not readable. So either this extension should have two variants or the background colour is fixed to white or similar.
i have a big project with about 30 files but the Lcov decorations are not display on the editor, and when I access the Lcov report and click on each...
Took me a while to figure out what was going on. The two are likely parsing paths differently when they shouldn't be.