PowerShell / PowerShell/PowerShellEditorServices
Slow performance for alias lookup
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
In Visual Studio Code, the ctrl + F5 keyboard shortcuts translates PowerShell command aliases. The performance of this leaves a lot to be desired, and sometimes results in a confusing end user experience when you're rapidly moving the cursor around the editor.
Can we improve performance of this function, to make it more usable? If necessary, we could cache a lookup table, and either invalidate it on-demand, or periodically update it with a background worker.
Cheers,
Trevor Sullivan
https://trevorsullivan.net
https://twitter.com/pcgeek86
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 identifies the PowerShell alias lookup triggered by the Visual Studio Code ctrl+F5 shortcut, but names no file, test, or entry point. Trace that lookup first and establish a reproducible rapid-cursor performance case; done means the lookup is measurably more usable without the confusing behavior described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell, vscode
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100