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 the language server starts, we walk the whole workspace, checking each folder we encounter.
Instead of scheduling all jobs as soon as we encounter a directory, we could check if the directory contains any files relevant to the language server (.tf, .tf.json, .tfvars, .tfvars.json, …) and take a note of if by scheduling a discovery job. In the new discovery job, we create the necessary state entities and can decide if it makes sense to schedule further jobs. Or create small state entries (just Path) during walking and do everything else on open.
The text was updated successfully, but these errors were encountered:
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.
When the language server starts, we walk the whole workspace, checking each folder we encounter.
Instead of scheduling all jobs as soon as we encounter a directory, we could check if the directory contains any files relevant to the language server (
.tf
,.tf.json
,.tfvars
,.tfvars.json
, …) and take a note of if by scheduling a discovery job. In the new discovery job, we create the necessary state entities and can decide if it makes sense to schedule further jobs. Or create small state entries (justPath
) during walking and do everything else on open.The text was updated successfully, but these errors were encountered: