Turn off warnings until a check is requested by the developer

[jhowa1]

"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.

[bergmeister]

This issue rather belongs to the vs code PowerShell extension because only with the context that a variable has just been typed, could a temporary suppression happen but I think most other languages exhibit this behaviour as well.
https://github.com/PowerShell/vscode-powershell

[SydneyhSmith]

Thanks, I will transfer this issue to the /PowerShell/vscode-powershell repo

[rjmholt]

We do currently have a delay built in with a cancellation mechanism, so that diagnostic analysis is not rerun or published until almost a full second after you finish typing.

Instead, do a code review on demand to make this check and any other checks on request.

I don't believe VSCode has a mechanism to make such a request currently; their presumed architecture (which we follow) is that diagnostics are run when the file is opened or changes. While it may be possible for us to invent such a mechanism, it's not clear what that should look like (we're open to suggestions). How should users request diagnostics?

Given that this is the first time such a feature has been requested, I'll leave it as up-for-grabs for now. If more demand accumulates, we may be able to reprioritise.

[jhowa1]

Some editors will put the warnings in a separate panel, with each warning having a link to the line requiring attention. Here are other ways to remove the intrusion of warnings in the middle of writing the line of code that are simple and have been used.

• Use a command button to turn on/off warnings
• Use a control key sequence to turn on/off warnings. And example would be Control-W to do this.

Spyder handles the warning issue nicely, however it clearly lags in other features compared to Visual Code.

[rjmholt]

Some editors will put the warnings in a separate panel, with each warning having a link to the line requiring attention

Just as an FYI, in VSCode this is the Problems pane