PowerShell / PowerShell/vscode-powershell
Turn off warnings until a check is requested by the developer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
"UseDeclaredVarsMoreThanAssignments" warning appears while typing the bloody variable in for the first time. To make it worse, a lightbulb obscures the name of the variable making the code
While the idea to make this check makes sense, doing so while typing code in is beyond annoying. It gets in the way. Instead, do a code review on demand to make this check and any other checks on request.
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 does not name any files, tests, or entry points. Start by locating where diagnostics and the lightbulb are produced in the VS Code PowerShell extension, then determine how an explicit code-review request could trigger checks. Done means the named warning and other checks no longer appear while typing and run only after a developer requests them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100