Skip to content

powershell.codeFormatting.pipelineIndentationStyle:IncreaseIndentationAfterEveryPipeline does not support pipeline chain operators. #5251

@Null-Fault

Description

@Null-Fault

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.

Summary

When using a pipeline chain operator, e.g. &&, with the setting powershell.codeFormatting.pipelineIndentationStyle:IncreaseIndentationAfterEveryPipeline configured, it does not indent when doing separate lines. Regular pipeline indentation works fine.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.4.11
PSEdition                      Core
GitCommitId                    7.4.11
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Name             : ConsoleHost
Version          : 7.4.11
InstanceId       : 84549210-57a7-4bc4-b715-cb1dbeb4ccd7
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-US
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

Visual Studio Code Version

1.102.3
488a1f239235055e34e673291fb8d8c810886f81
x64

Extension Version

Steps to Reproduce

Get-Item "C:\someItem" &&
Get-Item "C:\someItem"

Press 'Format'. Nothing happens. It should do this:

Get-Item "C:\someItem" &&
Get-Item "C:\someItem"

Visuals

No response

Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-Script AnalysisIssue-BugA bug to squash.Needs: Author FeedbackPlease give us the requested feedback!Pending: ExternalThis issue is not fixed here, it is fixed in a dependent repo such as PowerShell,PSScriptAnalyzer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions