Invoke-Formatter loses one level of identation after chain with more than 2 commands and script blocks

Steps to reproduce

Input script, formatted already as expected.

Function a {
    Function b {
        Get-Content blah | ? {
            $_ -match foo    
        } | Set-Content bleh

        $AnotherStatement = 1
    }

    Write-Host "hi"
    b
    exit 1
}

a

Expected behavior

The example above after formatted looks the same.

Actual behavior

After a chain of more than 2 commands which spans several lines, the formatter loses one level of indentation. Using $(...) triggers the same problem.

Function a {
    Function b {
        Get-Content blah | ? {
            $_ -match foo
        } | Set-Content bleh

    $AnotherStatement = 1
}

Write-Host "hi"
b
exit 1
}

a

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.15063.1805
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.1805
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.18.3

Commencez par reproduire le comportement signalé avec Invoke-Formatter et le script PowerShell de l’issue, y compris le pipeline comportant plusieurs commandes et la variante $(...). Suivez le point d’entrée du formateur et vérifiez que le formatage préserve l’indentation d’origine des instructions qui suivent ces chaînes et ces blocs de script.