Closed andyleejordan closed 1 year ago
We were using our own UI, not the byzantine internal UI where it actually needed to be fixed.
This is https://github.com/PowerShell/PowerShellEditorServices/pull/2023 but again, with the right UI.
And not only have we tracked this down, we were finally able to reproduce it (and so test this fix).
Resolves https://github.com/PowerShell/vscode-powershell/issues/3991.
P.S. This is actually like take five.
We were using our own UI, not the byzantine internal UI where it actually needed to be fixed.
This is https://github.com/PowerShell/PowerShellEditorServices/pull/2023 but again, with the right UI.
And not only have we tracked this down, we were finally able to reproduce it (and so test this fix).
Resolves https://github.com/PowerShell/vscode-powershell/issues/3991.