Should native command errors have the executable path or invocation as the TargetObject instead of the name? #15992
Description
Summary of the new feature / enhancement
In #15897 we added in the executable name as the ErrorRecord TargetObject at the last minute.
But when we write the error, we also have:
- The whole process object of the executable
- The start info object
- And on that, the executable path and arguments
Would it be better/more helpful to make any of those the TargetObject?
Proposed technical implementation details (optional)
No response