CodeFormattingOTBS settings preset always fails due to conflicting rules

[RylandDeGregory]

Steps to reproduce

1. Define a script that contains custom object syntax

# Build output object and add to array
$ServerArray += [PSCustomObject]@{
    ComputerName = $VMName
    vCenterName = $vCenter.name.Split('@')[1]
}

1. Run PSScriptAnalyzer with the built-in 'CodeFormattingOTBS' settings preset.

Invoke-ScriptAnalyzer -path ./test.ps1 -Settings 'CodeFormattingOTBS'

1. Note that PSAlignAssignmentStatement rule throws a Warning.

2. Correct error by aligning assignment statements.

# Build output object and add to array
$ServerArray += [PSCustomObject]@{
    ComputerName = $VMName
    vCenterName  = $vCenter.name.Split('@')[1]
}

1. Run PSScriptAnalyzer with the built-in 'CodeFormattingOTBS' settings preset again.

Invoke-ScriptAnalyzer -path ./test.ps1 -Settings 'CodeFormattingOTBS'

Expected behavior

No errors.

Actual behavior

PSUseConsistentWhitespace throws an error due to the multiple spaces before the assignment operator =.

This also happens when using the -Fix parameter of Invoke-ScriptAnalyzer. It will simply switch back and forth between the two errors each time you execute the command with -Fix.

Environment data

MacOS Catalina 10.15.5

[bergmeister]

This looks like a duplicate of #769, would you agree?
I think a fix for this is not very easy because it involves both rules knowing about each other. A possible but expensive solution would be to try merge the rules together into one, which is something that even the previous maintainer of PSSA has suggested to do.
cc @rjmholt as some food for thought for PSSA v2 API

[RylandDeGregory]

This looks like a duplicate of #769, would you agree?
I think a fix for this is not very easy because it involves both rules knowing about each other. A possible but expensive solution would be to try merge the rules together into one, which is something that even the previous maintainer of PSSA has suggested to do.
cc @rjmholt as some food for though for PSSA v2 API

I'd agree that it is a duplicate. But, I'd also pose 2 question to the maintaining team.

1. If this has been a known issue for over 3 years with 7 duplicate issues, why has it not been prioritized for resolution?
2. As mentioned in Unable to use both AlignAssignmentStatement and UseConsistentWhitespace rules #769 by @jayvdb, why are the default settings profiles all still using these conflicting rules together? It seems that users are being guided to failure by including multiple broken default configurations.

[JamesWTruher]

@RylandDeGregory please feel free to provide a PR to address this issue.

[RylandDeGregory]

@RylandDeGregory please feel free to provide a PR to address this issue.

#1559

[ghost]

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