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
The paths should be relative to the root of the folders in the workspace (not sure if we want to allow for initialization outside workspace scope, maybe as a follow-on issue to investigate).
Given the above config and the following tree structure for a single workspace folder:
The extension should enumerate all the directories in the setting that match actual directories present and pass those to the LS. In this case it would be:
[
"dir1",
"dir2/dir3"
]
(You'll notice otherDir is not passed as it doesn't match anything on disk, and someDir is not passed as its not in the settings).
Optionally we may also want to support per root module expanded configuration.
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
locked and limited conversation to collaborators
Aug 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Users' should be able to manually override root modules for a given Terraform workspace or folder. The config should be scoped
resource
.The paths should be relative to the root of the folders in the workspace (not sure if we want to allow for initialization outside workspace scope, maybe as a follow-on issue to investigate).
Given the above config and the following tree structure for a single workspace folder:
The extension should enumerate all the directories in the setting that match actual directories present and pass those to the LS. In this case it would be:
(You'll notice
otherDir
is not passed as it doesn't match anything on disk, andsomeDir
is not passed as its not in the settings).Optionally we may also want to support per root module expanded configuration.
The text was updated successfully, but these errors were encountered: