blakeembrey / blakeembrey/make-error-cause
Could `toString()` show causes?
Open
enhancement
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I have to remember to import `fullStack` and use it when logging errors. It would be convenient if make-error-cause would override `Error.prototype.toString()` to print the causes as well. Perhaps that's considered too much of a change from the standard Error behavior?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.