| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The `juliosueiras/terraform-lsp` project readme says:
> The aim to have a unified lsp for terraform in the future, but for now there is two concurrent development with collabration to each other, this repo is aim for more experimental features, and the terraform-ls is aim for stableness
Hashicorp's seems to be more actively developed nowadays as well.
https://github.com/hashicorp/terraform-ls
|
| |
|
|
|
| |
VSCode extensions are so large size and we offten get a network error with downloading them.
So we had better to directory download package.json.
|
| |
|
|
|
| |
`terraform init` creates .terraform/ and is a better indicator of the
root than .git/ in many cases
|
| |
|
|
|
|
| |
notification
related with #127
|
| |
|
|
| |
configs.lua set settings vim.empty_dict() as default
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
`nvim_lsp/skeleton.lua` is not really a skeleton, it's a `configs`
class that provides
1. actual functionality
2. a bunch of configs
Each config is added to the `configs` object (FKA "skeleton") as
a property. Those configs are not "templates", they are "configs". So we
should clean up the wording in various places to say "config" instead of
"skeleton"/"template".
Closes #64
|
| |
|
