Allow using workspaceFolder placeholder variable for more portable sandbox configurations #424
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #374
Allows using
${workspaceFolder}
for the sandbox setting's manifest/switch/template. Since this only replaces the variable, it's done during the JSON serialization/deserialization. Relative paths are still not supported, so no command execution logic was changed.In a workspace editor, it resolves
${workspaceFolder}
with the path of the first workspace folder. If no workspace folders are open,${workspaceFolder}
is resolved with the value ofProcess.cwd
.When selecting a sandbox, if the path of the workspace folder appears in a discovered configuration, it will be substituted with
${workspaceFolder}
. This makes the sandbox configurations portable by default.