Incorrect semantic highlighting for block braces

[pjmiravalle]

When editor.semanticHighlighting.enabled is set to true in vscode, it causes an issue with syntax highlighting for resource/data block declarations.

Specifically, the curly brace bracket(s) after resource "type" "name" is wrapped in the same syntax highlighting token that is used for "type" "name", which causes the bracket to take on the wrong color in the editor. Hopefully that makes sense.

My guess is that the recent additions of this extension dipping its toes into using semantic tokens (#523) is causing this to occur.

editor.semanticHighlighting.enabled ENABLED

This also seems to happen for data resource declarations:

editor.semanticHighlighting.enabled DISABLED

[radeksimko]

Thank you for the detailed report, I managed to reproduce this with the following minimal config:

resource "aws_iam_role_policy" "firehose_s3_access" {

}

Given that this highlighting is provided by the language server it's also likely where it can be fixed, so I'm going to transfer the issue there.

[radeksimko]

I just raised a PR with fix #390, which once reviewed and merged will be part of the next LS release. VS Code in particular should then download and install the new version of LS automatically on launch and fix the problem there.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.