only show TODO code lens on lines that start with a comment token

[joshspicer]

fix for #7954 being far too verbose.

[connor4312]

I suggest adding * (with surrounding spaces_ for JS/TS docblock comments too, and /// for Rust and C# docblock styles

[joshspicer]

nice

[TylerLeonhardt]

This seems suspicious. It's something that would be language specific too.

<!-- TODO: ...... -->

/*
TODO: some multi-line
comment with context
*/

<#
TODO: PowerShell block comments are weird
I know
#>

https://github.com/microsoft/vscode/blob/55f06131905f07dde60f301aa56be6e2f52155a3/extensions/make/language-configuration.json#L2-L7

The comment syntax is declared by the language support, I feel like we should somehow leverage that if we can.

[TylerLeonhardt]

https://github.com/microsoft/vscode/blob/55f06131905f07dde60f301aa56be6e2f52155a3/src/vs/editor/common/languages/languageConfigurationRegistry.ts#L35-L47

we have this in core... and we have a number of commands in core that are about retrieval of symbols:
https://code.visualstudio.com/api/references/commands#commands

I wonder if this warrants some way to get the LanguageConfiguration via a Command. Or at least just the comment stuff...

@hediet @alexdima I see your name around this code, maybe you have ideas

[joshspicer]

Thanks for the pointers, this looks a lot more correct.

I justified that this was ok since it's configurable via a setting and did not know we could possibly leverage core for this information.

[alexr00]

I don't think we should have two setting that both control whether the code action/codelens show.

Can we instead just remove "BUG" from the list of defaults?

[joshspicer]

@alexr00 I still think it's incorrect to match outside of a comment. Do you disagree?

@TylerLeonhardt thanks for the idea/pointers