Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Add command for clearing coverage highlight #601

Closed
zmb3 opened this issue Nov 3, 2016 · 5 comments
Closed

Add command for clearing coverage highlight #601

zmb3 opened this issue Nov 3, 2016 · 5 comments

Comments

@zmb3
Copy link
Contributor

zmb3 commented Nov 3, 2016

The Go: test coverage in current package command is great, but once you run it there's no way to clear the coverage.

Can we add a command to clear the coverage highlighting? Or even change the existing command to a toggle command?

@ramya-rao-a
Copy link
Contributor

That would be a nice feature. PRs are welcome!

@brandonblock
Copy link

Just wanted to add that I'd warmly welcom this feature.
I've never worked with TypeScript, but may be willing to give it a shot

@gabrielgatu
Copy link

I was having the same problem the other day and I've made a search of the pull requests for test-coverage hoping for an easy solution to clear highlights and I've found this: #143, i.e. just type something and the highlight will disappear (leaving here for further reference).

The toggle idea is a good one (my first try), however since then it would be a good idea to include inside the readme a section for test coverage, explaining how it works and the current solution for removing highlight.

What do you think?

@ramya-rao-a
Copy link
Contributor

@gabrielgatu I agree that this needs to be documented, but I wonder if README is the right place for it. It is already so huge and has a lot of content about set up

#596 was created to track adding details about the features of this extension, how to use it, tips and tricks etc.

I'd say wiki would be the right place.

@ramya-rao-a
Copy link
Contributor

The command Go: Test Coverage In Current Package is renamed to Go: Toggle Test Coverage In Current Package and it does exactly what the name suggests.

This change is out in the latest update (0.6.60)

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants