Formatting doesn't handle the property with ANSI escape sequence string value properly, which leads to color leaking

[thegraffix]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues, especially the pinned issues.

Exception report

N/A

Screenshot

Environment data

PS Version: 5.1.19041.1645
PS HostName: ConsoleHost
PSReadLine Version: 2.2.2
PSReadLine EditMode: Windows
OS: 10.0.19041.1 (WinBuild.160101.0800)
BufferWidth: 106
BufferHeight: 3000

Steps to reproduce

Happens on PS 5.1 console and Windows Terminal app (cannot reproduce with the ISE nor PowerShell 7.2.2)

To reproduce:

1. Type Get-PSReadlineOption | Format-List *

To resolve:

1. Type Get-PSReadLineOption (without | Format-List *) and color scheme is restored after the property CommandColor is listed on-screen. See bottom screenshot for a better explanation of this.

Expected behavior

Color scheme should remain constant

Actual behavior

• Console color scheme now appears like the ListPredictionSelectedColor color scheme
• Missing property values (see screenshot)
• Clearing the screen/changing console size doesn't resolve the issue.

[daxian-dbw]

This is an issue with the PowerShell formatting. When using Format-List *, the formatting view registered by the PSReadLine module won't be used. Instead, PowerShell formatting will dump every property of the object and display them in a list view.

The problem is that PowerShell formatting doesn't handle ANSI escape codes properly. The color properties are all holding ANSI sequences for color, which should not be simply written to console as regular strings. And doing so will lead to color leaking, which is what is observed in your screenshot. I will transfer this issue to PowerShell repo.

[ghost]

🎉This issue was addressed in #17262, which has now been successfully released as v7.3.0-preview.4.:tada:

Handy links:

• Release Notes