vscode extension is over hinting, including variable

[aboveyunhai]

UnoCSS version

not applicable, latest Unocss vscode extension v0.57.1

Describe the bug

The latest unocss vscode is running correctly, but it over hinting, cause confusion on reading regular variable, shouldn't it check string only?.

For the typescript, it's very tricky since it's a valid string, so I can't tell it's the intention, fixable or not, but I will leave it here as reference.

Reproduction

install the unocss vscode extension and use the example code from screenshot.

System Info

Windows 10

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[louiss0]

This is a problem that I see as well. I don't know why Uno does this.

[f820602h]

In single-file Vue development, this problem will also occur.
The underscore will appear in the text within the style section, even though it is not an UnoCSS class.

[rick-ast]

I also get the unexpected hints in css file.

[antfu]

This is how UnoCSS works by scanning for occurrence. I initially designed VS Code extension that way it's more consistent with the runtime behavior, but yeah I agree this can be annoying at some point. I think we could treat VS Code a bit, especially by only highlighting a certain context.