PowerShell / PowerShell/vscode-powershell
Support for VSCode variables and arguments when defining Additional Exe Paths
Open
Nobody has claimed this yet.
Issue-Enhancement
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
The PowerShell Additional Exe Paths setting only accept absolute path. This feature request is about getting that setting to resolve vscode's predefined variables and to accept arguments such as -NoLogo, -NoExit, and -Command.
Proposed Design
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation of the PowerShell Additional Exe Paths setting in the VS Code extension and review how it currently handles absolute paths. Determine how VS Code predefined variables and executable arguments should be represented, then verify that the setting resolves variables and accepts arguments such as -NoLogo, -NoExit, and -Command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100