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

Add support for coverage markup #80

Closed
newhook opened this issue Nov 24, 2015 · 9 comments
Closed

Add support for coverage markup #80

newhook opened this issue Nov 24, 2015 · 9 comments

Comments

@newhook
Copy link
Contributor

newhook commented Nov 24, 2015

I've been using gocov and gocov-html (https://github.com/matm/gocov-html) to generate coverage diagrams for my tests. It would be awesome if it was possible to get these integrated into vscode-go.

@tecbot
Copy link

tecbot commented Nov 24, 2015

Did you try out https://github.com/joefitzgerald/go-plus for atom? I really like the integrated highlighting of code coverage inside the editor, so you don't need to switch to something else to check the code coverage :).
But don't now if it's possible to change the background color of some code positions in vscode.

@newhook
Copy link
Contributor Author

newhook commented Nov 24, 2015

I think it could use the diagnostics to do this. For example, DiagnosticSeverity.Information, or Hint.

@egamma
Copy link
Member

egamma commented Nov 24, 2015

@tecbot look into the support for decorators in the VS Code API. Here is an example https://github.com/Microsoft/vscode-extension-samples/tree/master/decorator-sample

@newhook
Copy link
Contributor Author

newhook commented Nov 24, 2015

That's a 404.

@lukehoban
Copy link
Member

@egamma Look's like the vscode-extension-samples is still private - not sure if that is intentional or not?

@tecbot See setDecorations for part of the API for working with decorations. There's also an extension doing some code coverage rendering here: https://github.com/bmeck/vscode-code-cover/blob/master/lib/ui.js

@egamma
Copy link
Member

egamma commented Nov 24, 2015

Fixed the vscode-extension-samples is now public.

@tecbot
Copy link

tecbot commented Nov 25, 2015

Thanks for your hints! Really helpful :)

@tampajohn
Copy link
Contributor

@tecbot I've taken a stab at adding coverage highlighting in #143, trying to keep it close to what we're used to in Atom (only highlights current package files for example). Also added a "get test coverage in this package" command...

@lukehoban
Copy link
Member

Looks like this issue didn't get closed after #143 was merged. I believe everything that was part of the ask here is available now.

@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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants