New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revisit default formatting of ErrorRecord #4674
Labels
Issue-Discussion
the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif
Issue-Enhancement
the issue is more of a feature request than a bug
Resolution-Duplicate
The issue is a duplicate.
WG-Engine
core PowerShell engine, interpreter, and runtime
Milestone
Comments
SteveL-MSFT
added
WG-Engine
core PowerShell engine, interpreter, and runtime
Issue-Discussion
the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif
Issue-Enhancement
the issue is more of a feature request than a bug
labels
Aug 25, 2017
@SteveL-MSFT: This is essentially what #3647 is about. I was about to post something there. Do you want us to continue here instead? |
I whole heartedly agree. BTW for script developers, I'd love to see something like Jeffrey's old
|
@mklement0 I'll resolve this as a dupe of yours #3647 |
This was referenced Nov 27, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Issue-Discussion
the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif
Issue-Enhancement
the issue is more of a feature request than a bug
Resolution-Duplicate
The issue is a duplicate.
WG-Engine
core PowerShell engine, interpreter, and runtime
The current formatting of ErrorRecord isn't useful enough for developers and too much unactionable
content for regular end users. Proposal on how to fix this will end up being a RFC, but we can discuss it here first. Perhaps the verbosity of the format is user-settable. There is also the problem of special casing formatting of ErrorRecord.
Steps to reproduce
Expected behavior
Actual behavior
Environment data
The text was updated successfully, but these errors were encountered: