PSUseConsistentWhitespace - Ability to ignore if in a line with multiple pipes

Summary of the new feature

The various PSUseConsistentWhitespace rules have various issues that might never be solved:

• https://github.com/PowerShell/PSScriptAnalyzer/issues?q=is%3Aissue%20state%3Aopen%20UseConsistentWhitespace%20sort%3Acreated-desc

My biggest issue is that I don't want it to touch one liners or multiliners like this:

(
    (
        Invoke-RestMethod -Method 'Get' -Uri 'https://api.github.com/repos/chocolatey/choco/releases'
    ) | Where-Object -Property 'prerelease' -NE $true
).'tag_name' | Sort-Object -Property @{'Expression' = {[System.Version]$_}} -Descending | Select-Object -First 1

Which becomes this:

(
    (
        Invoke-RestMethod -Method 'Get' -Uri 'https://api.github.com/repos/chocolatey/choco/releases'
    ) | Where-Object -Property 'prerelease' -NE $true
).'tag_name' | Sort-Object -Property @{'Expression' = { [System.Version]$_ } } -Descending | Select-Object -First 1

If I could tell PSScriptAnalyzer to ignore cases like that I'd be happy.

Current impact

This makes it so that I don't use the code formatting presets, and instead define all the rules manually and disable most of the PSUseConsistentWhitespace rules.

Side note: Would be great with the ability to override built-in presets, so you don't have to specify all the rules.

• 2017-03-07 "Add ability to inherit settings": https://github.com/PowerShell/PSScriptAnalyzer/issues/791
• 2024-12-01 "Code formatting preset - Add ability to override settings set by preset": https://github.com/PowerShell/vscode-powershell/issues/5109

Proposed technical implementation details (optional)

Don't know. Some ideas:

• Ability to ignore if more than one pipe `| is found on the same line?

What is the latest version of PSScriptAnalyzer at the point of writing

v1.24.0

Review the current PSUseConsistentWhitespace rules and the linked open issues to understand how whitespace is applied across pipelines. Define the exact behavior for lines containing multiple pipes, then verify that the proposed ignore behavior preserves existing formatting checks without affecting other cases.