Currently debugging exceptions can be tricky since lot of the exceptions get caught and reraised as different QWeb equivalent type.
This usually helps us to identify whether or not the exception has been considered during development.
However on some occasions this exception type changing obfuscates the original exception and can make debugging very tedious.
Improve exception handling traceability by going through each in the except block QWeb code base and on type changing raises use raise QWebException(e) from e instead of plain raise QWebException(e) in order to preserve the stacktrace.
Error messages should also be assessed and improved where necessary.
Currently debugging exceptions can be tricky since lot of the exceptions get caught and reraised as different QWeb equivalent type. This usually helps us to identify whether or not the exception has been considered during development. However on some occasions this exception type changing obfuscates the original exception and can make debugging very tedious.
Improve exception handling traceability by going through each in the
except
block QWeb code base and on type changingraises
useraise QWebException(e) from e
instead of plainraise QWebException(e)
in order to preserve the stacktrace. Error messages should also be assessed and improved where necessary.