Christoph Bergmeister

@Kriegel You need to use the `-Raw` option instead because `-ScriptDefinition` expects a string: ```` powershell Invoke-Formatter -ScriptDefinition (Get-Content -Path 'C:\MyFile.ps1' -Raw) ````

@Kriegel You're welcome. I had many cases in the past where `-Raw` was the better option and recently even when having to write tests that not only work with PowerShell...

I see that this issue has quite a few upvotes. Can anyone please provide details of a use case? Because VSCode has already integrated Invoke-Formatter, I do not understand why...

@Kriegel Thanks for the feedback. This sounds more like we could at least document an automation snippet because gluing stuff together is what PowerShell is for. The reason why implementing...

@felixfbecker You can, `Invoke-ScriptAnalyzer` supports that, the most common way is to use Pester integration in CI for PSSA checks. Either specify your custom format in a PSSA setting file...

@metablaster Invoke-Formatter has a `-Settings` switch already. As mentioned before, you could still script it yourself at the moment with something like ```pwsh Get-ChildItem -Recurse '*.ps*' | ForEach-Object { Set-Content...

The vs-code extension basically has individual settings for (most) settings of the formatting rules that you can specify in the psd1, therefore I consider them equivalent. People use the settings...

As per PSSA 1.19.0 release post [here](https://devblogs.microsoft.com/powershell/psscriptanalyzer-pssa-1-19-0-has-been-released/), PowerShell 7 syntax support has been added (mainly in PR #1331 and #1426). The markdown doc is more of an example but should...

Nice idea but you'd need to fix existing tests

I will try look into it another time and see whether I can do something about it, definitely before next release, sorry it's taken so long