Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

powershell.codeFormatting.pipelineIndentationStyle is ignored when formatting code #2732

Closed
SetTrend opened this issue May 30, 2020 · 3 comments
Labels
Resolution-Duplicate Will close automatically.

Comments

@SetTrend
Copy link

I am experiencing a problem with the powershell.codeFormatting.pipelineIndentationStyle setting: No matter what value I set it to, it seems to be ignored:

PowerShell

Environment Information

Visual Studio Code

Name Version
Operating System Windows_NT x64 10.0.18363
VSCode 1.45.1
PowerShell Extension Version 2020.4.0

PowerShell Information

Name Value
PSVersion 7.0.1
PSEdition Core
GitCommitId 7.0.1
OS Microsoft Windows 10.0.18363
Platform Win32NT
PSCompatibleVersions 1.0 2.0 3.0 4.0 5.0 5.1.10032.0 6.0.0 6.1.0 6.2.0 7.0.1
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)
Extension Author Version
powershell ms-vscode 2020.4.0
vscode-hexdump iliazeus 1.8.2
vscode-language-pack-de MS-CEINTL 1.45.1
@ghost ghost added the Needs: Triage Maintainer attention needed! label May 30, 2020
@SydneyhSmith
Copy link
Collaborator

Thanks @SetTrend this looks like a duplicate of PowerShell/PSScriptAnalyzer#1496

@SydneyhSmith SydneyhSmith added Resolution-Duplicate Will close automatically. and removed Needs: Triage Maintainer attention needed! labels Jun 2, 2020
@SetTrend
Copy link
Author

SetTrend commented Jun 2, 2020

Thanks, Sydnay, for replying.

I'm not sure, because in the other issue I can't see no pipeline character. The sample code provided therein is dealing with curly braces indendation, not with pipelining.

The other issue may probably be closed due to the option setting not being applicable to the provided sample code.

What do you think? If you believe both issues are dealing with the same issue and will be treated equally, please feel free to close my issue.

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Jun 2, 2020
@ghost
Copy link

ghost commented Jun 4, 2020

This issue has been marked as duplicate and has not had any activity for 1 day. It has been closed for housekeeping purposes.

@ghost ghost closed this as completed Jun 4, 2020
@SydneyhSmith SydneyhSmith removed the Needs: Maintainer Attention Maintainer attention needed! label Jun 4, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate Will close automatically.
Projects
None yet
Development

No branches or pull requests

2 participants