Replies: 1 comment
-
Looks like I found a workaround. I'm modifying the [[language]]
name = "hcl"
file-types = ["hcl", "nomad"]
language-servers = []
[[language]]
name = "tfvars"
file-types = ["tf", "tfvars"] The question still stands, is there a cleaner way to "inherit" (lacking a better word) a language definition overriding some of it's definitions? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an annoying issue with LSP enabled for
*.hcl
files. By defaulthcl
files are set to useterraform-ls
but it usually is not right.While it's true that a
.tf
hashcl
syntax it's lsp setup is most likely wrong creating all sort of useless error reports.Example:
This is an
hcl
file, it doesn't contain terraform resources and it's not part of a terraform module, it's a terragrunt configuration file that orchestrates a terraform module.Overriding the
hcl
definition works but I would have to re-write another entry for actualtf
files using the same options ashcl
except the lsp configuration.Is there another way to split file extensions in different language entries? Should I simply remove
.hcl
extension from thehcl
filetype definition?Beta Was this translation helpful? Give feedback.
All reactions