Describe your idea
Currently, if an error is caught and a new error (eg, with a better description) is rethrown, it will include the traceback at the point the new error is thrown. We may want to have information about the original error, namely its stack trace.
Motivation
Easier debugging
Proposed Solution
We should probably make use of Error.cause, setting it when "rethrowing" errors and using it when logging/showing error details eg in the error dialog
Other Information
Covering related concerns: #797 #796 #794
Describe your idea
Currently, if an error is caught and a new error (eg, with a better description) is rethrown, it will include the traceback at the point the new error is thrown. We may want to have information about the original error, namely its stack trace.
Motivation
Easier debugging
Proposed Solution
We should probably make use of
Error.cause, setting it when "rethrowing" errors and using it when logging/showing error details eg in the error dialogOther Information
Covering related concerns: #797 #796 #794