Include more information in `DebugMiddleware`.
See original GitHub issueRight now we just display a raw format_trackback()
.
It’d make sense to have a proper page with lines of context around each file in the stack, and local variables at each point. (As with Django or Werkzeug’s debugger pages)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Debug the problems in Middleware - SAP Community
Hello experts, Can anybody please tell me how to learn debug the error in middleware..? is there any material available..?? if so how...
Read more >Debugging Express
Express uses the debug module internally to log information about route matches, middleware functions that are in use, application mode, and the flow...
Read more >debugging - How do I make a custom middleware function get ...
The reason why I'm trying to create this property is due to this Koa documentation (see link below) which states that we can...
Read more >Debug a bot with inspection middleware - Microsoft Learn
Learn how to use inspection middleware to debug bots. See how to use the Bot Framework Emulator to inspect state data and message...
Read more >Plack::Middleware::Debug - MetaCPAN
DESCRIPTION. The debug middleware offers a configurable set of panels that displays information about the current request and response.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
What about integrating the werkzeug debugger itself? This feature was there previously in APIStar.
I’d be happy to take ideas from the Django and Werkzeug implementations. Werkzeug’s debugger is WSGI-based, so a clean port of it would need some adapting.
I’d suggest approaching this iteratively, let’s start with a bit more info and some basic styling, then work on things from there.