Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Should native command errors have the executable path or invocation as the TargetObject instead of the name? #15992

Copy link
Copy link
@rjmholt

Description

@rjmholt
Issue body actions

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

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.