John Blackbourn
John Blackbourn
These are the enhancements I want to make to the AJAX debugging in Query Monitor. Short term: - [ ] Use more appropriate `console` methods, such as `console.warn()` for warnings...
MVP. Logs calls to `switch_to_blog()` and `restore_current_blog()` on a Multisite installation and shows the corresponding site IDs, caller, and component in a table.
This starts us down the path of switching over Query Monitor's output to client-side rendered React components. This has numerous benefits including: * Better performance (no need to render a...
Query Monitor 4.0 will bump the minimum required version of PHP to 7.2. This facilitates that change, removes various back-compat code, and modernises some functionality. Entry points will remain compatible...
I've been hacking around with the idea of switching QM's output to a web component so its styles are isolated and then I don't need to worry about forcibly overriding...
I want to remove Dashicons as a dependency so QM's stylesheet is standalone and can ultimately be output without being enqueued. The idea is that QM itself should not impact...
This introduces a new panel which allows you to track the journey that a `WP_Error` object takes through the code. Requires WordPress 5.6 (see https://core.trac.wordpress.org/ticket/40568). The instantiation of the error...
Exposes some extra information in the Request panel when a request results in a 404. See #342
Probably too much in here. Need to decide how to make this useful rather than potentially overwhelming.