PowerShell / PowerShell/PowerShellEditorServices

Add Get-EditorCommand and $psEditor.GetEditorCommand()

Open
#251 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Extension Terminal Issue-Enhancement
Dominant language
C#
Stars
767
Forks
266
Avg merge
3d 16h
Merged PRs (30d)
1

Description

The way it is currently setup, it can be very difficult to determine what the Editor Command Names are that are loaded. The user is only shown the Display Name, so they will actually have to go look at the source code of the Register-EditorCommand to get the name.

This makes it difficult to unregister Editor Commands if you do not already know exactly what the command's name is. This will become more problematic once people start integrating their commands into modules.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing Register-EditorCommand flow and how loaded editor commands are currently displayed. The change is complete when users can discover editor command names through Get-EditorCommand and $psEditor.GetEditorCommand(), making those names available for unregistering.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.