GeezerVison

In 1.25.0, PSUseConsistentIndentation double-indents the body of an attribute that opens a scriptblock, such as [ArgumentCompleter({ … })] or [ValidateScript({ … })]. The body gets two levels and the closing })] gets one.

# 1.25.0 output
[ArgumentCompleter({
		Param($commandName, $parameterName)
	})]

# Expected (current main)
[ArgumentCompleter({
	Param($commandName, $parameterName)
})]

Root cause / status

• The cause is the same as PSUseConsistentIndentation: Hashtable inside method call gets double-indented #2159: the ( and the { on the opener line each add an indentation level.
• Improve pipeline indentation handling in UseConsistentIndentation rule #2173 already fixes this on main, though no release includes it yet. When a ( is followed on the same line by an opener that stays unclosed, the ( skips its increment and its matching ) skips the decrement. The check doesn't care what comes before the (, so [Attr({ is covered too.

Changes

• Tests only, no rule changes. Two cases are added to the "When multiple openers appear on the same line" context in Tests/Rules/UseConsistentIndentation.tests.ps1:

  • top-level [ArgumentCompleter({ … })], using the issue's example
  • [ValidateScript({ … })] nested inside a function's param() block

  Both start from double-indented input and check that it is corrected. They fail against 1.25.0, so a regression would be caught.

• Fixes PSUseConsistentIndentation double-indents attribute bodies that open a scriptblock ([Attr({ … })]) #2216