Skip to content
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

Code complete not working in vs code #384

Closed
chrisgallivan opened this issue Jun 12, 2020 · 4 comments
Closed

Code complete not working in vs code #384

chrisgallivan opened this issue Jun 12, 2020 · 4 comments

Comments

@chrisgallivan
Copy link

I have version 2.0.1 of the extension installed in vs code 1.46.0

I can't get the code completion to work.

I type a resource block in azurerm, and nothing happens to assist me.

@ghost
Copy link

ghost commented Jun 12, 2020

I open a issue like that at #383

@tnightengale
Copy link

tnightengale commented Jun 17, 2020

There appears to be a lot of issues with the new 2.0.1 version. To summarize my understanding thus far:

  • every old feature besides highlighting (formatting, auto-complete) is now configured through the language server
  • there is a stable language server supporting terraform 0.12, however when trying to enable the language server, 2.0.1 requires a .terraform file in the root of you VScode folder that you have opened (annoying for users that open a larger project where tf is a sub folder)
  • some people have circumvented the above issue by adding a dummy .terraform file in their root that they work in, but frankly this seems like a hack - and ostensibly would require adding .terraform files to any parent folder that opens to be "root" when opening it in VScode
  • personally I downloaded the vsix for 1.4.0 and will be using that (despite the lack of 0.12 language support) until all these issue get fixed up

@paultyng
Copy link
Contributor

paultyng commented Jul 7, 2020

Going to merge this with hashicorp/terraform-ls#32. Additional folder configurations are now supported, and we will be allowing users to easily configure/list their root module directories in #423

@paultyng paultyng closed this as completed Jul 7, 2020
@ghost
Copy link

ghost commented Aug 7, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants