Justin Grote

@flowchartsman totally forgot about devtools for this. I saw the same 

Only workaround I'm aware of is revert the extension to a version prior to the issue.

@conwnet I would think maybe there's some way for me to specify some sort of configuration file (e.g. github1s.json) that you could just import as a sort of workspace.json? Great...

> > Please note that this would probably only work with JavaScript-based language servers (so that they can run in browser). For Python, that would be https://github.com/microsoft/pyright, for example. >...

@bergmeister related to this, simply redirecting to a file, a common operation which does not actually produce an output, triggers the info as a false positive  Workaround: Use Out-File...

Thanks for submitting! I think this needs to be done as a PSScriptAnalyzer rule which will be read as a formatter, you may need to submit there. @bergmeister?

I am in the `-not` camp, despite it being a terrible syntax in if statements. I would definitely turn on this rule on my project styles but this is one...

I had to fully disable the rule because I couldn't get a suppress attribute to work anywhere in this pester test (The UpdateGithubReleaseCommonParams gets used as a splat in future...

@jaykul A workaround is to set the variables in the BeforeAll at Script scope it seems.

Appreciate the feedback, and I'm aware of this aspect, hence why I was trying to limit the scope. Analysis across multiple files is an issue as mentioned, and the goal...