Automatically split | characters to a new line

[thomasrea0113]

Summary of the new feature/enhancement

I should state that I am using VS Code. I was told that for this feature to be possible in VS Code, it has to first be implemented here. The setting I mention down below is a VS Code Powershell setting.

I'd like to the ability to take the following line:

$Ports | ForEach-Object -Process { NETSTAT.EXE -ano | findstr.exe :8080 | ForEach-Object -Process { ($_ -split '\s+')[-1] } | Sort-Object | Get-Unique | ForEach-Object -Process { taskkill.exe /F /PID $_ } }

and convert it to:

$Ports |
    ForEach-Object -Process {
        NETSTAT.EXE -ano |
            findstr.exe :8080 |
            ForEach-Object -Process {
                ($_ -split '\s+')[-1]
            } | Sort-Object |
            Get-Unique |
            ForEach-Object -Process {
                taskkill.exe /F /PID $_
            }
    }

I think this would go a long way in approving readability. At the very least, with the

"powershell.codeFormatting.pipelineIndentationStyle": "IncreaseIndentationForFirstPipeline"

setting enabled, when I manually add the new line after each |, { , and }, it will format the indentation correctly which is nice.

[bergmeister]

For some preliminary triage info, please refer to the original issue #2194
Thinking about this again, how do you think the rule should treat simple one line expressions like foo | bar? It would be annoying if those were to be split across 2 lines. Something like requiring the number of pipes to be greater than 2? We have a new AvoidLongLines rule by @thomasrayner , maybe we could incorporate that into this rule to split a pipeline expression into more than 1 line to make it fit into the line length limit as an alternative to always splitting every expression across 1 line?

[thomasrea0113]

For some preliminary triage info, please refer to the original issue #2194
Thinking about this again, how do you think the rule should treat simple one line expressions like foo | bar? It would be annoying if those were to be split across 2 lines. Something like requiring the number of pipes to be greater than 2? We have a new AvoidLongLines rule by @thomasrayner , maybe we could incorporate that into this rule to split a pipeline expression into more than 1 line to make it fit into the line length limit as an alternative to always splitting every expression across 1 line?

I think merging this request with a AvoidLongLines rule would work perfectly. For shorter lines, There's no need to break them up. The above formatting should only take be applied when necessary. eslint handles this fantastically.