the coverage markers don't allow enough room to click for a breakpoint

[boneskull]

between the black line and the marker is where you gotta click.

[ArtemGovorov]

Good point, I've always used keyboard shortcut for that so missed it.

[hellboy81]

@boneskull Which library have you used for DI?

[boneskull]

@hellboy81 I don't understand..?

[hellboy81]

In beforeEach section, .__Rewire__

In rewire I have used .__set__ to replace privates with stubs

[boneskull]

@hellboy81 Ah. It's not rewire proper, it's babel-plugin-rewire

[IPWright83]

That's interesting - in VS2015 I'm getting those coverage markers within the code. I actually thought that I'd prefer them outside in the breakpoint bar, but now I'm not so sure.

[ben-moore]

Any update on this issue? I have this in VSCode - I can set breakpoints with mouse or keyboard, but the coverage markers obscure the red markers that indicate a breakpoint is set.

[ArtemGovorov]

@ben-moore I have reported the issue to the VS Code repo - microsoft/vscode#5923

[shahata]

maybe there's a way to change the opacity of those markers so we'll be able to see the breakpoint underneath? or is it not really underneath?

[ArtemGovorov]

@shahata Unfortunately VS Code internally is replacing the background, so as you said - it's not underneath.

[mcintyre321]

Could wallaby not spot that there is a breakpoint there and use a custom background image with an overlaid breakpoint?

[ArtemGovorov]

@mcintyre321 Unfortunately there's no extension API to query/get notified if a breakpoint is set.

[mcintyre321]

:(