ConvertFrom-StringData mistakenly emits a statement-terminating error when one of its input strings isn't well-formed

[mklement0]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

With multiple, individual strings as input, ConvertFrom-StringData mistakenly aborts processing overall, via a statement-terminating error, once an incorrectly formatted string is encountered; the expected behavior would be to merely emit a non-terminating error in that event, and continue processing further inputs:

'foo=bar', 'broken', 'bar=baz' | ConvertFrom-StringData

As an aside:

• For potential improvements to ConvertFrom-StringData in this context, see Make ConvertFrom-StringData more error tolerant #23790 (comment)

Expected behavior

Name                           Value
----                           -----
foo                            bar
ConvertFrom-StringData: Data line 'broken' is not in 'name=value' format.
bar                            baz

That is, processing should have continued after the incorrectly formatted input string, and the output should be two hashtables, one for each valid input string.

Actual behavior

Name                           Value
----                           -----
foo                            bar
ConvertFrom-StringData: Data line 'broken' is not in 'name=value' format.

That is, overall processing was unexpectedly aborted when the broken input string was encountered.

Error details

No response

Environment data

PowerShell 7.5.0-preview.2

Visuals

No response

[237dmitry]

It ignors all of input strings, outputs them to host but you cannot set variable:

$res = 'a = 1', 'b = 2', 'c' | ConvertFrom-StringData     # $res is not defined
$res = 'Music', 'Fake', 'Pictures' | Get-item             # $res without "Fake"

[mklement0]

Good point, @237dmitry: Because the error that is emitted is statement-terminating, you cannot even capture the hashtables that are created for the well-formed input strings, because this requires collecting the pipeline output, and since the error terminates the whole pipeline, no assignment is performed.
This problem too will go away once a non-terminating error is emitted instead.