When the ROPAGATE_EXCEPTIONS is set, it is desirable to re-throw the error such that any registered flask error handlers will take care of it.
This fixes the error described in issue #162.
Coverage remained the same at 90.772% when pulling 68d0faa8def56517bdce4df5cac13bb94985a97b on JortdeBokx:master into b44bc08b11213d49fadae873650d3555889052ec on miLibris:master.
Coverage remained the same at 90.772% when pulling 1421fee0dbed8b891b3f9c7fe7342dc6939455e6 on JortdeBokx:master into b44bc08b11213d49fadae873650d3555889052ec on miLibris:master.
I support this change. It gives users the option to fully customize the error handling. Not all users will be happy with the particular error handling that is enforced otherwise.
When the
ROPAGATE_EXCEPTIONS
is set, it is desirable to re-throw the error such that any registered flask error handlers will take care of it. This fixes the error described in issue #162.