Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

coverage overlay is not visible

See original GitHub issue

Environment

node -v: 9.11.1
npm -v: 5.6.0
Operating system: Debian

Steps to Reproduce

clone https://github.com/seanpoulter/vscode-jest-181
open vscode

Expected Behavior

coverage overlay is visible in the editor.

Actual Behavior

coverage overlay is not visible.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

ThomasRooneycommented, May 12, 2018

@seanpoulter @phra – I spent a few hours and worked it out after this bugged me today – both the lack of markers and the annoyance that the red line is in the wrong place.

Its because the jest executable isn’t switched based on OS, so windows fails when it tries to run the shell script (instead of the ‘cmd’ file). The markers are due to using a hardcoded 0 => 6 column definition in the ‘diagnoses’ visual studio code API, instead of using the ‘whole line’ equivalent.

0reactions

seanpoultercommented, May 21, 2018

Let me know if you need a hand. I’m going to close this since I’ve been able to see the code coverage on an Ubuntu image using the example repo - https://github.com/seanpoulter/vscode-jest-181.