Historically the debugger component of In-Portal (one that is shown on F12 press and has yellow/pink reports) was built to be independent from In-Portal core:
I think that we should make it more In-Portal friendly by:
- moving out debugger into separate namespace
- extracting profiler component out from debugger
- include jQuery from CDN whenÂ
jQueryvariable not present on a page instead of duplicating code locally - store debugger runs in database for easy management
- record several debugger runs per page (main page + all ajax requests)
- unique request key is GET+POST+URL+REFERER (for ajax requests)
- associate ajax requests back to main page from which it was made so we can see whole requests together
- don't delete debugger report after it was viewed
- redesign debugger UI to allow seeing ajax request reports as they are created
- create separate sections in debugger for following (see below) instead of mixing all together:
- error/warning/notice
- request data
- external requests (curl, db, memcache)
- other
Basically we're going into Phabricator-alike DarkConsole tool:
