refactor: introduce standardized error messages and stacktraces #869
Conversation
anshchaturvedi
changed the title
anshchaturvedi
force-pushed
the
DX-660-introduce-stacktraces
branch
from
6c4f2ad to
6f754f1
Compare
Introduces `[INFO]`, `[WARN]`, and `[ERROR]` prefixes to error messages to make them easier to read and understand when debugging. The hope is that we remain consistent with this formatting across the codebase. Ticket: DX-660
This adds a stacktrace as a string alongside the message passed to the E.left. Ticket: DX-660
Adds a utility function to strip stacktraces off of errors since they are machine/platform dependent and cannot hard-code them into tests. Ticket: DX-660
anshchaturvedi
force-pushed
the
DX-660-introduce-stacktraces
branch
from
5eababd to
c11dc0e
Compare
|
🎉 This PR is included in version @api-ts/openapi-generator@4.29.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/io-ts-http@3.2.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/express-wrapper@1.0.30 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/superagent-wrapper@1.3.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@1.1.10 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
2 participants
This update adds
[INFO],[WARN], and[ERROR]prefixes to error messages to make them easier to read and understand during debugging. It also includes stack traces forE.leftreturns outside ofcli.tsto help with troubleshooting.How logging looks:
How errors look:
Ticket: DX-660