Jake Bolton

Using this config, does it stop mutating your code? If not, my full config which does not mutate is here: https://gist.github.com/ninmonkey/1c1ab3fcaa6776e754679598231fc26b *[1] ```json { "powershell.codeFormatting.whitespaceBetweenParameters": false, "powershell.codeFormatting.useCorrectCasing": true, "powershell.codeFormatting.autoCorrectAliases": true,...

> @rjmholt this seems to not occur with just PSSA If `Invoke-ScriptAnalyzer` is returning multiple `ParserError`s, shouldn't `Invoke-ScriptFormatter` exit without attempting to format? That combined with certain flags seems to...

This likely won't do anything, but, what if you set the environment's encoding to non-BOM UTF8? ```ps1 $global:OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new() ```

> even more copies of the portable vscode install, each with their own settings Yes. You can have that same effect with zero portable installs. You can use: ```ps1 code...

@corbob: >All formatting related rule properties are settable via the powershell.codeformatting.* settings My original examples weren't great. This new one shows that - there's a formatting setting that the extension...

> See [PowerShell/PSScriptAnalyzer#1402 (comment)](https://github.com/PowerShell/PSScriptAnalyzer/issues/1402#issuecomment-704418988) ~~@rjmholt I think I found another case. Going through that thread it didn't have a case with a syntax error in `param()` blocks. (they were always...

### Describe bug or problem **Update:** There's currently 2 parts: 1. **bug** : The formatter is ran when the script has parse errors / can't run. (Verses the linked thread...

This caused by `PSReadLine` itself # Error Case: 1. Create a filename that requires surrogate pairs, include a `🖥️` or `😀` 1. copy a path to your clipboard 1. type...

I was having trouble getting tracing to log when running. I was able to figure out it seems to be in an infinite loop It keeps running down until line...

Here is a similar error where `@( String )` fails to coerce to `[string[]]` when using a `List[String]` ```ps1 # works [Collections.Generic.List[Object]]$names = 'bob', 'jen' $names.AddRange(@( 'sue', 'bill')) # errors...