code coverage: gutter type coverage covers breakpoints

[saurabhsuniljain]

When code coverage gutter is displayed, not able to add/delete/modify breakpoints, there was an already issue filed for this in the old repo.

Old Issue: microsoft/vscode-go#1715

If there is any workaround anyone has found please let me know.

[hyangah]

The upstream issue is microsoft/vscode#5923 and still no solution.

Wonder if we can come up with a less intrusive highlight display.

/cc @pjweinbgo

[saurabhsuniljain]

For, now I found a workaround you can change the type for code coverage in setting as highlight.

It is not a good experience but it is a workaround for when you want to debug and check code coverage at the same time.

[pjweinbgo]

we could have a statusBar-only choice, perhaps. That's the red/green marks on the right.

…

On Mon, Aug 31, 2020 at 2:29 PM Saurabh Jain ***@***.***> wrote: For, now I found a workaround you can change the type for code coverage in setting as highlight. It is not a good experience but it is a workaround for when you want to debug and check code coverage at the same time. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#588 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACL4QJCLPAM7W5YUCO6O5MTSDPTYRANCNFSM4QQF7WTA> .

[schuster-rainer]

You can use F9 for setting the breakpoint. Or depending on your keybinding what "set breakpoint" is mapped to

[thomaspaulin]

Bump: The upstream issue was closed as fixed in April of 2023.

[hyangah]

Thanks @thomaspaulin
Looks like the issue that caused gutter to cover breakpoints is indeed resolved.

However, microsoft/vscode#95992 is still open - setting new breakpoints still doesn't work. :-( Users still can add new breakpoints with F9.

[connor4312]

Fyi we are finalizing (in next week's 1.88 release) official support for test coverage, and using that avoids the issue microsoft/vscode#123713