You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, currently the debugger middleware HTML response has two sections, Error and Request. What do you think of a new section Stacktrace/Backtrace? This would then print the backtrace provided by Printexc.get_backtrace ().
Some context:
When I'm building an application and I start out with a bunch of failwith "TODO" placeholders (or god forbid someone uses partial functions 😱 ), I at some point find myself looking for raised Errors a lot or writing an ad-hoc backtrace printer. I thought we could simply include it in Opium.
Let me know what you think! I'll gladly provide a PR if you deem it sensical :)
The text was updated successfully, but these errors were encountered:
Hello, currently the debugger middleware HTML response has two sections,
Error
andRequest
. What do you think of a new sectionStacktrace
/Backtrace
? This would then print the backtrace provided byPrintexc.get_backtrace ()
.Some context:
When I'm building an application and I start out with a bunch of
failwith "TODO"
placeholders (or god forbid someone uses partial functions 😱 ), I at some point find myself looking for raisedError
s a lot or writing an ad-hoc backtrace printer. I thought we could simply include it in Opium.Let me know what you think! I'll gladly provide a PR if you deem it sensical :)
The text was updated successfully, but these errors were encountered: