PowerShell / PowerShell/vscode-powershell
Command Explorer: add a catalog as there are too many commands
Open
Nobody has claimed this yet.
Area-Command Explorer
Issue-Enhancement
Up for Grabs
- 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
There are too many commands, so it's hard to find the command you want.
It's better if there is a similar design like PowerShell ISE
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
The issue provides no file, test, or entry point. Start by locating the existing Command Explorer and reviewing the linked PowerShell ISE design reference. Define the catalog behavior and scope before implementation; done requires an agreed design and a working catalog that makes commands easier to find.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100