Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syntax Highlighting for Successive Interpolated Values Incorrect #1118

Closed
NJITman opened this issue May 26, 2022 · 2 comments
Closed

Syntax Highlighting for Successive Interpolated Values Incorrect #1118

NJITman opened this issue May 26, 2022 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@NJITman
Copy link

NJITman commented May 26, 2022

Versions

Extension

v2.22.0

VS Code

1.67.2 (system setup)

Operating System

Windows 10 21H2

Terraform Version

1.1.8

Steps To Reproduce

When creating a string using interpolation, if two interpolated values are placed one after the other with no intervening characters, TF VSC extension shows second interpolation as being text. It does not generate a plan error, so it is acceptable to use in TF and generates the proper results. However, the TF linter is showing the second interpolation as text when it should show it as an interpolated value.

In the example below, compare the highlighting of bucket_name (has intervening period between two interpolated values) and aliases (does not have any intervening characters).

Image 002

Expected Behavior

All interpolated values should be displayed with proper syntax highlighting.

Actual Behavior

If two interpolated values are placed one after the other, the first interpolated value is shown with correct highlighting, while the second is shown with text highlighting.

Additional context

@NJITman NJITman added the bug Something isn't working label May 26, 2022
@radeksimko radeksimko added this to the 2.23.0 milestone May 26, 2022
@radeksimko
Copy link
Member

Hi @NJITman
I can verify this is duplicate of #1040 which was addressed by hashicorp/syntax#34 / #1114.

It will be part of the next release v2.23.0.

Screenshot 2022-05-26 at 08 20 43

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants