PowerShell / PowerShell/vscode-powershell
Add MRU to argument prompt when debugging a PowerShell script
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Summary of the new feature
When one debugs a PowerShell script with the "PowerShell Launch Current File w/Args Prompt" configuration:
{
"type": "PowerShell",
"request": "launch",
"name": "PowerShell Launch Current File w/Args Prompt",
"script": "${file}",
"args": [
"${command:SpecifyScriptArgs}"
],
"cwd": "${file}"
},
the input field is pre-filled with the most recent arguments input on the previous debug session.
It would be useful to have a list of most recently used argument lists, so that one could easily test the same script with several sets of arguments.
Proposed technical implementation details (optional)
The list should be sorted by most-recently used argument list.
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 with the PowerShell Launch Current File w/Args Prompt configuration and the ${command:SpecifyScriptArgs} input described in the issue. Trace how the prompt is populated and determine where its recent argument lists are handled. Done means the prompt offers previously used argument lists in most-recently-used order.
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