v2021.9.0
Thursday, September 09, 2021
This release includes changes from both v2021.8.3-preview and v2021.9.0-preview.
A new stopDebugger notification was added that allows PowerShell Editor Services,
the LSP module, to stop an attached UI debugger (such as VS Code's)
for debugger sessions started by executing code with a PSBreakpoint attached.
This may not work in all cases but should improve usability.
The PowerShell status bar indicator no longer uses custom coloring but instead pulls from the user's theme.
A formatting bug was fixed by community maintainer Patrick Meinecke.
A regression in the debug launch configuration's script parameter was fixed and covered with a test.
And finally, the bundled PSScriptAnalyzer
was updated to v1.20.0.
vscode-powershell
- ✨ 📖 vscode-powershell #3544 - Document the trace server setting is valid (despite Code's warning). (Thanks @michal037!)
- #️⃣ 🔍 vscode-powershell #3522 - Allow PowerShell session to start and stop the debugger interface.
- ✨ 📺 vscode-powershell #2436 - Use status bar colors from theme instead of hardcoded values.
- ✨ 🚨 vscode-powershell #3529 - Extend CI test matrix and update readme(s).
PowerShellEditorServices
- 🐛 📟 PowerShellEditorServices #24977523 - Implement
LengthInBufferCellsto fix ANSI formatting. (Thanks @SeeminglyScience!) - ✨ 🔍 vscode-powershell #3522 - Send
stopDebuggernotification when appropriate. - 🐛 🔍 vscode-powershell #3537 - Fix bug with
ExecuteScriptWithArgsAsyncwhenscriptis a command. - ✨ 🕵️ PowerShellEditorServices #1562 - Pin PSScriptAnalyzer to
v1.20.0, Plaster tov1.1.3and PSReadLine tov2.1.0.