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
Today the workspaceFolder property requires workspaceMount to be in non-dockerCompose scenarios. Given processing for devcontainer.json should mount the location of the .git folder unless workspaceMount is set, it is reasonable to allow this property to be set independently.
In this scenario, the following syntax could be used to connect to a relative path to the detected auto-mount location.
To avoid confusion, if workspaceMount is specified, or this is a Docker Compose scenario, ${containerWorkspaceFolder} would be treated like "". We could also introduce a different variable here instead (e.g. defaultContainerWorkspaceFolder) that had these same smarts in it.
The text was updated successfully, but these errors were encountered:
Today the
workspaceFolder
property requiresworkspaceMount
to be in non-dockerCompose scenarios. Given processing fordevcontainer.json
should mount the location of the.git
folder unlessworkspaceMount
is set, it is reasonable to allow this property to be set independently.In this scenario, the following syntax could be used to connect to a relative path to the detected auto-mount location.
To avoid confusion, if
workspaceMount
is specified, or this is a Docker Compose scenario,${containerWorkspaceFolder}
would be treated like""
. We could also introduce a different variable here instead (e.g.defaultContainerWorkspaceFolder
) that had these same smarts in it.The text was updated successfully, but these errors were encountered: