PowerShell / PowerShell/vscode-powershell
Enable "Trigger Parameter Hints" for available method/constructor overloads
Nobody has claimed this yet.
- 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
Today, available method/constructor overloads are shown when you get to the method body or an open parens
However, if you are already in a closed parens and want to see the available method/constructor overloads, this is not available, you have to delete the closed parens and retype them to get the prompt again.
Proposed Design
The C# extension wires up to Trigger Parameter Hints when in the method/constructor parameter body, we should do the same.
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 by locating the existing method/constructor parameter-hint handling in the VS Code PowerShell extension and compare it with the C# extension's wiring for Trigger Parameter Hints. Verify the behavior inside a closed parameter list, where available overloads should appear without deleting and retyping the closing parenthesis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100