-
Notifications
You must be signed in to change notification settings - Fork 6
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
unable to use absolute file paths #21
Comments
Sorry, been very busy lately. Yes, I think the current design assumes that the coverage files are in the open workspace. |
Thank you for the offer but this time I even had not looked at a solution.
That's nice. |
Any chance to inspect that, yet? |
Hey, sorry, been extremely busy. I'm working on it now, a fix should be here this week. I might build a version for you to test before release it, would you have some slack sometime this week to test? |
I should be able to test that shortly after a test .vsix is made availabe anywhere. |
vscode-koverage-0.0.13-beta.vsix.zip |
Test result: the path issues are all gone, there is only no calculation if the config is broken. |
Can I have a screenshot and a bit more details on what you mean by "config is broken"? (Thanks for your help) |
This comment was marked as resolved.
This comment was marked as resolved.
I can confirm that upcoming 0.13 fixes both this and #22 |
Project is stored in "/home/project" (so that's the workspace folder), the build is done in "/tmp/project" (and therefore coverage files are to be found there.
The following setup does work with coverage-gutters, but doesn't with koverage
koverage output says:
Is the configuration wrong or does Koverage really not support absolute names yet (I didn't get it working with ../ entries either)?
The text was updated successfully, but these errors were encountered: