You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When editor launches the LS on behalf of the user, it will attempt to index all initialized modules within the hierarchy.
Some users open directories which are relatively high up in the hierarchy, meaning that there is many directories to walk through, which in turn may consume CPU and filesystem I/O resources.
This is why we also avoid descending into certain directories which will never contain editable Terraform modules.
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 details necessary to investigate further.
Use-cases
When editor launches the LS on behalf of the user, it will attempt to index all initialized modules within the hierarchy.
Some users open directories which are relatively high up in the hierarchy, meaning that there is many directories to walk through, which in turn may consume CPU and filesystem I/O resources.
This is why we also avoid descending into certain directories which will never contain editable Terraform modules.
terraform-ls/internal/terraform/module/walker.go
Lines 22 to 29 in ac2194d
Users may however have additional directories in their workspace which they would like to ignore.
Proposal
Make the ignorelist configurable via options, similar to how other aspects of LS are configurable
terraform-ls/internal/settings/settings.go
Lines 16 to 28 in ac2194d
The text was updated successfully, but these errors were encountered: