Add an option to remove bullets near tests

[kachkaev]

Environment

1. node -v: 9.5
2. npm -v: latest yarn
4. Operating system: macOS High Sierra

Steps to Reproduce

Hi again guys. I switched to VSCode just recently and am very happy to find your extension! Can easily imagine using it nearly every day in future!

I understand the value of showing green, red or empty bullets next to it("...", func) – that's a nice contextual feedback. However, I guess I just stumbled across a case when it'd be great to turn these marks off and would like to know if that's possible. Check out this example:

As you've probably already guessed, the test is marked as skipped because its name is dynamic, so there's no way of knowing its actual state. I've got quite a few of such tests and it feels natural to disable the bullets. I haven't found a config variable to do so, but if it's just a lack of my attention, sorry for the buzz!

Perhaps, an even more sophisticated strategy could be applied in such cases?

[orta]

IMO, I think we should just remove all dots on dynamically named it/tests.

I think that work would need to happen inside jest-editor-support - https://github.com/facebook/jest/tree/master/packages/jest-editor-support

Basically extending this to check whether the AST inside the ( and ) is just a single string

[kachkaev]

Yeah, that'd be useful. Despite that, an option to remove all dots would be a useful thing too. It may be something to do with my perception, but I can't get used to them and am unconsciously trying to delete them from time to time 😃

[orta]

Sure, makes sense, happy to take an PR adding that option too

[MichalLytek]

Would be possible to move the bullets to the side, where breakpoints are placed? Just like in wallaby,js or mocha-sidebar:

[kachkaev]

@19majkel94 this array of marks looks much easier to glance through!

[seanpoulter]

It's possible, and it's a medium-sized PR if you'd like to give it a shot.

[kachkaev]

@19majkel94 would you like to give it a go? I've got only one week of experience in VSCode, need to mature a bit first 😅

[MichalLytek]

@kachkaev I've never done anything related to VSCode extensions 😞
I may try but now not, I have some work to do in my open source project.

[github-actions]

This issue has been inactive for over a year and has been marked as stale. It will be automatically closed in 30 days if no further activity occurs. Since significant changes have occurred in the codebase, please open a new issue with updated details if the problem still persists.