[LSP] Words surrounded by back quotes should be blue in markdown comments

Describe the bug Previously if you surrounded a word with back quotes it would turn blue in a markdown comment (triple slash), but it no longer does with LSP.

To Reproduce Add this comment:

/// `this should be blue`

Expected behavior Back quotes should emphasize things as before.

Screenshots

Versions (please complete the following information):

• VS Code version:

1.57.0-insider
Commit: b95b73b7b074f5dddccd57e5e290617f1a767ec1

• Dart extension version: 3.22.0
• Dart/Flutter SDK version:

Flutter 2.3.0-0.1.pre • channel unknown • unknown source
Framework • revision d72bfb8d07 (12 days ago) • 2021-04-26 06:05:55 -0700
Engine • revision de6e1adf97
Tools • Dart 2.14.0 (build 2.14.0-18.0.dev)

[DanTup]

@jducaud yep, understood. The difference between your screenshots is really the difference between LSP semantic tokens or the textmate grammar. The reason it works without the extension enabled now is that in the recent release of VS Code includes the textmate grammar from this extension directly in VS Code.

If you want to disable semantic tokens for now until this is addressed, you can add the following to your VS Code user settings:

"[dart]": {
	"editor.semanticHighlighting.enabled": false
}

This will result in the same colouring as your first screenshot without needing to disable LSP or the extension. It does mean a few things may not be coloured correctly due to limitations of the regular expressions (for example if you name a method set it’ll be coloured like the set keyword instead of a method), though you might it’s worth the trade-off.

[jducaud]

Thank you @DanTup! This trick is a good provisional workaround