Add a CR to CommandNotFoundException error string#4934
Conversation
We're here at PowerShell Unplugged at Ignite, and this error message could *really* use a carriage return!
SteveL-MSFT
left a comment
There was a problem hiding this comment.
Thanks for the contribution, but string resources should not contain newlines as it may produce unexpected results when it goes through FormatAndOutput
| </data> | ||
| <data name="CommandNotFoundException" xml:space="preserve"> | ||
| <value>The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.</value> | ||
| <value>The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program. |
There was a problem hiding this comment.
Formatting should be handled by FormatAndOutput. String messages should not contain newlines.
There was a problem hiding this comment.
Perhaps adding new newlines is something we should consider for other strings as it can improve readability.
|
Please clarify what was idea here. After the change: Or idea was to change command line error formatting? To: |
|
@SteveL-MSFT Could you please clarify? |
|
@iSazonov I believe the intent was to have the next sentence on the next line left justified. The whitespace should have been removed. I'll submit PR. |
We're here at PowerShell Unplugged at Ignite, and this error message could really use a carriage return!