You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using VSCode Version: 1.58.2, OS: Linux x64 5.8.0-63-generic snap (Ubuntu 20.04.2)
Currently a resource type and resource identification are recognized as string. As such the color syntax is not very readable. Can you please add new editor scopes for:
Terraform resource_type
Terraform resource_name
To allow to configure the corresponding element with a different color syntax. The attached screenshot shows the desired effects using IntelliJ IDEA v2021.2
tringuyen-yw
changed the title
[Feature request] Color syntax: add scope for resource_type and resource_identification
[Feature request] Color syntax: add scope for resource_type and resource_name
Aug 2, 2021
Hi folks,
While #934, hashicorp/terraform-ls#802 and made it possible to distinguish between plain strings and labels I just wanted to note that we plan to still look into the original proposal - that is distinguishing between the resource type and name.
We track that under hashicorp/terraform-ls#803 as most of the relevant work will be done on the language server.
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 details necessary to investigate further.
Using VSCode Version: 1.58.2, OS: Linux x64 5.8.0-63-generic snap (Ubuntu 20.04.2)
Currently a resource type and resource identification are recognized as string. As such the color syntax is not very readable. Can you please add new editor scopes for:
To allow to configure the corresponding element with a different color syntax. The attached screenshot shows the desired effects using IntelliJ IDEA v2021.2
VS Code Color theme:
The text was updated successfully, but these errors were encountered: