Radek Simko

### Use-cases Users with more complex modules and many variables may not always notice mismatching types within variable files. For example, say we have the following variable declaration ```hcl variable...

### Use-cases Users with more complex modules and many variables may not always notice duplicate entries across multiple autoloaded variable files. For example, say we have the following variable files...

During the early development of LS prototype we exposed the completion through a custom command, outside of LSP: ``` Usage: terraform-ls completion [options] [path] Lists available completion items Options: -at-pos...

### Use-cases Terraform users can define a module version constraint via the `version` argument of a `module` block. For example: ```hcl module "eks" { source = "terraform-aws-modules/eks/aws" version = "~>...

### Current Version ``` 0.16.0 ``` ### Background Many users still doesn't seem to use the explicit provider specification via `required_providers` block, e.g. ```hcl terraform { required_providers { aws =...

## Use-cases ### Validity of References When collecting reference addresses (traversals) throughout a module, we also collect "constraints" based on where these references appear. This allows us to tell the...

### Current Version ``` 0.22.0 ``` ### Use-cases In majority of cases references in HCL2 are either plain dot-separated addresses, such as `aws_instance.example.private_ip`. There is however a few cases where...

Provide support for on-type formatting

2

### Current Version ``` 0.20.1 ``` ### Use-cases LS already provides the formatting method which allows clients/editors to format a whole file either on demand (via command palette) or on...

### Current Version ``` 0.22.0 ``` ### Use-cases See https://discuss.hashicorp.com/t/references-are-no-longer-detected-when-using-complex-types/29789 ### Proposal Modify https://github.com/hashicorp/hcl-lang to ensure that reference targets are collected not only for the block itself, but also for...

Consider reflecting custom working dir path (`TF_DATA_DIR`)

2

### Use-cases Currently the language server makes assumptions that all data directories are placed in the default location (within `.terraform` dir in the root of the module). Some users may...