v2022.11.1-preview butchers terminal prompt using WinPS 5.1

[Hetshu]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

Powershell Extension terminal prompt shows escape characters:

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.19041.1682
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1682
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.73.1
6261075646f055b99068d3688932416f2346dd3b
x64

Extension Version

[email protected]

Steps to Reproduce

Open a powershell script to activate the extension, switch to WinPS 5.1 and watch the prompt

Visuals

No response

Logs

No response

[PrzemyslawKlys]

Can confirm:

[DarkLite1]

Confirmed:

[andyleejordan]

Is shell integration supposed to work in PowerShell 5.1 in the first place? If not, I'll have to put a guard around it.

[andyleejordan]

Note: On Windows, you'll need PowerShell 7 (pwsh) for shell integration support.

Ahh.

[MrFly72]

Can confirm, too.
I have to go back to Production release, as I need to change between 5.1 and 7.x quite frequently as I have some old PSSnappin-Sh*t....

[andyleejordan]

@MrFly72 we've got a fix at the ready, and we got it upstream too! Sorry about the temporary inconvenience, but won't be a problem next preview!