GutterFormatter breaks clicking in gutter to create breakpoint

Environment

1. node -v: v12.16.1

2. npm -v: 6.14.5

3. npm ls jest or npm ls react-scripts (if you haven’t ejected): jest@26.0.1

4. your vscode-jest settings if customized:

   • jest.pathToJest? default
   • jest.pathToConfig? default
   • anything else that you think might be relevant? see below

5. Operating system: macOS 10.15.4

Prerequisite

• are you able to run jest test from command line? yes
• how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) jest (with npx fallback)

Steps to Reproduce

Turn on GutterFormatter in vscode settings Try clicking in the gutter to turn on/off a breakpoint

Expected Behavior

Breakpoint is toggled on/off for that line

Actual Behavior

Nothing happens. Breakpoint not toggled.

[markcarroll]

Sorry @connectdotz I missed your question back when you asked.

I like the gutter formatted because it doesn’t get in the way the same as the default one. With the default formatted I have to keep toggling coverage off when I am starting new code and then have to turn it on again later. When a file has little to no tests and coverage is on, it is very hard to read the contents of the file using the built in Dark+ theme.

The gutter formatter is nice in that it hows coverage in a more subtle but still useful manner.

I hear you on the gutter issue though and yes, the breakpoint on/off thing is a real problem.

Maybe if we could make the default formatter more subtle that would do the trick.

[stefaneidelloth]

The bug of non working break points is still there. You should remove the GutterFormatter if you cannot fix that. The customization of line cutter works as workaround for me. Maybe use less annoying appearance as a default.

I use Darcula/PyCharm theme and following settings for the uncovered lines:

.vscode/settings.json

{
"jest.coverageColors": {
      "uncovered": "rgba(35,35,35, 0.5)",
      "partially-covered": "rgba(255,215,0, 0.04)",
}
}