2 ms·
This has less to do with vim than with Terraforms poor LSP support. Vim/Neovim has had LSP support for some time with plugins and now built in natively. I use
by jamesappledev 5y ago
This has less to do with vim than with Terraforms poor LSP support.
Vim/Neovim has had LSP support for some time with plugins and now built in natively.
I use COC vim as it's the fastest to get started and I rarely have to do much config as it's based on VSCode and comes with sane bindings for go-to-def, refactoring and more.
https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim
https://github.com/prabirshrestha/vim-lsp https://github.com/prabirshrestha/vim-lsp
https://github.com/neovim/nvim-lspconfig https://github.com/neovim/nvim-lspconfig
You can try to use either of these implementations:
https://github.com/juliosueiras/terraform-lsp https://github.com/juliosueiras/terraform-lsp
https://github.com/hashicorp/terraform-ls https://github.com/hashicorp/terraform-ls
These are both fairly limited but you can see every editor (except intellij) uses this under the hood.
I've used them at companies with 300+ terraform repos and have never had much of an issue navigating/understanding TF through Vim.
- flippinburgers 5y agoBy no means am I placing the blame at vim's feet. I know it is a terraform problem. Do those projects allow me to follow a user defined variable to its definition?