Add option to filter out file/folder suggestions when completions are automatically triggered by a space
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- powershell, typescript
- Domain
- developer-experience, tooling
Research direction
Start by locating the extension's automatic completion handling and the path that produces file/folder suggestions after spaces. Reproduce the Clear-Disk example in VS Code and compare it with PowerShell ISE behavior. Done should include a clear option that suppresses file/folder suggestions for space-triggered completions while preserving other completion behavior.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
I think the constant file/folder completion suggestions are distracting and I'd like to reduce those distractions. For example, if I type in a command like: Clear-Disk -Number 0 -RemoveData -RemoveOEM it will show unwanted file completions 4 times, once after the command and once for every space after each parameter/parameter value.
If you repeat this experiment in ISE you will note that it doesn't show any file completions. This is because ISE filters out file/folders from the automatic IntelliSense that is triggered by space.
Ideally something would be done about this in PowerShell itself to but unfortunately support for 5.1 has to be considered as well so adding an option in the extension would be nice.
Proposed Design
No response
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 548
- PR merge metrics
- No merged PRs in 30d
Getting set up
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.
More from PowerShell/vscode-powershell
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/vscode-powershell#5615 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
PowerShell/vscode-powershell#5607 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PowerShell/vscode-powershell#5599 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/vscode-powershell#5592 · 2 comments · 1 reaction ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
PowerShell/vscode-powershell#5583 · 1 comment ·
All issues in PowerShell/vscode-powershell
Similar issues
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mermaid-js/mermaid-live-editor#2053 ·
Maintainers usually reply within 1 day
-
factory
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jessepollak/home#1455 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
lingdojo/kana-dojo#31227 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
appandflow/stim#1838 ·
Maintainers usually reply within 1 day