IgnoreOneLineBlock=$false Correction Issue in PSPlaceOpenBrace and PSPlaceCloseBrace
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start by running the supplied Invoke-Formatter reproduction with PSPlaceOpenBrace and PSPlaceCloseBrace set to IgnoreOneLineBlock=$false, then trace those rule entry points in PSScriptAnalyzer. Done means the formatter produces the expected indentation and brace placement for this conditional, with regression coverage for the reported settings.
Written by the indexing model from the issue text.
Description
So far as I can tell, this hasn't been reported, but it is related to issue #2210 which I was also going to include. I've also gone through and applied the surfaced corrections one-by-one, which produces the exact same results in VS Code with the latest PowerShell extension (pre-release, 2026.1.2, which has PSScriptAnalyzer 1.25.0).
Steps to reproduce
Run the following command:
Invoke-Formatter -ScriptDefinition "if (`$RegEx) { '-match' } else { '-like' }" -Settings @{IncludeDefaultRules=$true;Rules=@{PSPlaceOpenBrace=@{Enable=$true;IgnoreOneLineBlock=$false;};PSPlaceCloseBrace=@{Enable=$true;IgnoreOneLineBlock=$false;}}}
Expected behavior
if ($RegEx) {
'-match'
} else {
'-like'
}
Actual behavior
if ($RegEx) {
'-match'
}
else {
'-like'
}
Environment data
> $PSVersionTable
Name Value
---- -----
PSVersion 7.6.6
PSEdition Core
GitCommitId 7.6.6
OS Microsoft Windows 10.0.22631
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.25.0
1.25.0
The settings passed, a little easier to read, if needed.
@{
IncludeDefaultRules = $true
Rules = @{
PSPlaceOpenBrace = @{
Enable = $true
IgnoreOneLineBlock = $false
}
PSPlaceCloseBrace = @{
Enable = $true
IgnoreOneLineBlock = $false
}
}
}
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 415
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PSScriptAnalyzer
-
Up-for-Grabs
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSScriptAnalyzer#2213 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
PowerShell/PSScriptAnalyzer#2217 · 1 comment ·
-
PSUseConsistentIndentation double-indents attribute bodies that open a scriptblock (`[Attr({ … })]`)Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2216 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PowerShell/PSScriptAnalyzer#2211 ·
-
`PSPlaceOpenBrace` and `PSPlaceCloseBrace` leave trailing whitespace when expanding one-line blocksOpen
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2210 ·
All issues in PowerShell/PSScriptAnalyzer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/onnxruntime-genai#2633 ·
Maintainers usually reply within 1 day
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
microsoft/semantic-kernel#14491 ·
Maintainers usually reply within 2 days
-
area:jobads-cv FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1878 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pnp/pnpcore#1878 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15331 · 2 comments ·
Maintainers usually reply within 1 day