Format-Table ignores custom columns widths except in the first column

[mklement0]

Related: #14677

Note: This bug affects Windows PowerShell too.

Steps to reproduce

$obj = [pscustomobject] @{ a='A'; b='1234567890'; c='C' }

# OK - custom width is in the *first* column.
$obj | Format-Table -Property @{ e='b'; width = 5 }, c | Out-String | Should -Match '1234…'

# !! BROKEN: custom width is (only) in a column *other* than the first:
$obj | Format-Table -Property a, @{ e='b'; width = 5 }, c | Out-String | Should -Match '1234…'

Expected behavior

Both tests should succeed.

Actual behavior

The 2nd test fails, because the custom column width was unexpectedly not applied.

Expected regular expression '1234…' to match ' a b          c - -          - A 1234567890 C  ', but it did not match.

Note that, similarly, custom widths in later columns only take effect if one was specified for and successfully applied to the first column.

Environment data

PowerShell Core 7.2.0-preview.2

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.