Replies: 2 comments 2 replies
-
Given exceptions are already being formatted, and this is an extension of that, it seems like a reasonable proposal. Plus the code on your branch is clean and covered by tests. I'm interested in what other people think about this idea too. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Since this has been merged, I'll go ahead and close this as resolved. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Sometimes in my console apps I use a convention, that defines that the app can raise a "business/user" exception that is meant to be displayed to the end user.
This kind of error is so descriptive that a Stack Trace actually adds more noise and confusion instead of helping the end user.
In those scenarios I want to print the Exception type and description, but without a stack trace.
For example:
How does it sound?
TBH... I have a PR ready on my fork, all checks have passed.
Beta Was this translation helpful? Give feedback.
All reactions