Skip to content

Conversation

@andyleejordan
Copy link
Member

This variable never could have accepted VS Code predefined variables because support for that is still an open feature request upstream. We have no API to resolve predefined variables in values given to contributed settings, and so cannot support this.

Resolves #4163

This variable never could have accepted VS Code predefined variables
because support for that is still an open feature request upstream. We
have no API to resolve predefined variables in values given to
contributed settings, and so cannot support this.
@andyleejordan andyleejordan requested a review from a team September 13, 2022 00:27
@ghost ghost added Area-Workspaces Issue-Bug A bug to squash. labels Sep 13, 2022
Copy link
Collaborator

@SeeminglyScience SeeminglyScience left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one minor wording suggestion

Co-authored-by: Patrick Meinecke <[email protected]>
@andyleejordan andyleejordan enabled auto-merge (squash) September 13, 2022 19:34
@andyleejordan andyleejordan merged commit df9f374 into main Sep 13, 2022
@andyleejordan andyleejordan deleted the andschwa/update-setting-docstring branch September 13, 2022 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workspace folder pick pops up if a predefined variable is used for the powershell.cwd setting

3 participants