-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature suggestion: inline coverage reporting #72
Feature suggestion: inline coverage reporting #72
Comments
From @patrys on January 17, 2017 8:53 Here's an example implementation for Golang: microsoft/vscode-go#143 |
From @cristim on July 27, 2017 10:34 Coming from golang I miss this a lot. |
While we don't have the time currently to implement this ourselves, we would consider a PR that could read the coverage report file from coverage.py and display coverage results from that. |
Hi! I actually need this feature and I can implement it but I need to discuss some details |
Please feel free to post your questions here and we'll be glad to assist you. |
First of all: which format of report should be implemented? |
That's completely upto you. Since you are writing the code, you need to decide what's best for you. Tip, using a json or similar format world be easier. I haven't checked what formats are available.
You could would need to display the information as code lenses. Users of this feature would want the information easily viewable, and code lenses are the way. Please check the vscode API (samples), on adding code lenses.
Not having checked the API, I have no idea. Since you are implementing this, it's upto you. As a start, just hardcode these, later we can add code that will allow users to configure them. |
I would actually specifically say you need to support what And wouldn't have a code lens on every line of code be hard to read? Or do code lenses also control the gutter? |
Yes of course coverage.py is most known tool, I'll focus on it.
In my opinion the best way to show coverage is gutters, but this approach produce an issue that you cannot set a breakpoint when coverage is enabled. Another way is to use code background decoration, but in this way it can be distractive a little bit |
Yes, I agree. For some reason I was thinking of profiling. Apologies. @litleleprikon |
Ok, got it. I will start with XML report of coverage.py, gutters and hardcoded settings. |
@litleleprikon |
@DonJayamanne Yeah, already did this and the average way is to use gutters or code background highlighting. Also Here is settings for // show or hide the gutter coverage
"coverage-gutters.showGutterCoverage": true,
// show or hide the line coverage
"coverage-gutters.showLineCoverage": false,
// show or hide the ruler coverage
"coverage-gutters.showRulerCoverage": false |
|
To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves. |
From @sfermigier on January 16, 2017 11:28
Issue #183 being now closed, here's an independent issue for a feature suggestion that I find really important: inline reports for
coverage.py
results (orpytest --cov
, etc.).Copied from original issue: DonJayamanne/pythonVSCode#647
The text was updated successfully, but these errors were encountered: