ConciseView mangles multiline errors thrown from scripts, but not from binary cmdlets #23833
Open
5 tasks done
Labels
Needs-Triage
The issue is new and needs to be triaged by a work group.
Prerequisites
Steps to reproduce
If a script throws a multi-line error using
throw
, all newlines are replaced with spaces. This does not happen with binary cmdlets and advanced functions using$PSCmdlet.ThrowTerminatingError()
. Structured error messages are much harder to read this way. Example from one of my scripts:Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: