-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow using "#" for line comments #313
Comments
Hi @khaliddermoumi, this extension is not meant to be used for Terraform (.tf) files, as described in the README. This extension uses the official HCL library rules as defined here: hclsyntax/spec.md which state no preference for which to use. There is no way to configure this, because VS Code itself does not provide a way for a user to do this. The official HashiCorp Terraform Extension uses |
Hi @jpogran! I am using the extension to edit terragrunt files (.hcl), which are authored in terraform syntax. You can't use the dedicated TF extension for this, as it would validate the terragrunt specific parts as "errors". vscode-hcl is the better choice, but it should use the "#" comment symbol for TF code (just like the TF extension). I am sure this is a common issue, as terragrunt is widely used by TF users. |
Hi I recently burnt way too much time trying to sort out what extensions are required for my new laptop to work on a Terragrunt project. I thought I'd got it sorted when I installed this one but the double slash comments are driving me insane as all of the code I'm working with is chock full of @jpogran says:
and
so who decided this one must use Please, please make it configurable or just change to the more widely used |
After some consideration and the discussion in this issue, we've decided to make This change will be part of the upcoming 0.6.0 release. |
Please support using "#" as the line comment character.
So far, the extension uses only "//", and there seems to be no way to configure this.
As "#" is the typical line comment character in Terraform, when using this extension with TF, it would be very desirable to have "#" in the hcl files too.
The text was updated successfully, but these errors were encountered: