Repository navigation
feat: Pollora and WordPress in Laravel Debugbar (phase 1) - #1
Merged
Merged
Conversation
Pollora tab (what answered the request, versions, discovery, modules, theme, async actions), WP Request, WP Queries, WP Hooks and WordPress phases on the timeline; REST and admin-ajax requests stored and tagged with phpdebugbar-id; qm/* and pollora/debugbar/* actions bridged. Extension points: the Collector base class and container tags for packages, the pollora/debugbar/register action for WordPress code.
Most of Pollora's callbacks are closures, which all read as "Closure": first-class callables now read as Class::method and real closures as the class and file:line they were written in. Tab icons are taken from php-debugbar's own set; any other name renders as an empty square.
ogorzalka
marked this pull request as ready for review
October 8, 2026 13:30
A Playwright job installs the skeleton under DDEV with this package, adds a fixture mu-plugin that extends the bar both ways (actions and a tagged Collector), and checks the tabs, their order, the answering template, wpdb queries, a REST call listed by the bar and the third party data.
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of the Debugbar integration spec.
Tabs
Route::wp(), template hierarchy + view, Laravel route, or WordPress alone), versions, discovery scans, modules, theme, async actions.$wpdbqueries in Debugbar's SQL widget (SAVEQUERIESturned on before WordPress loads), slow flag, soft/hard limits, main query marked.AbstractHook::all(), feat: AbstractHook::all() and the pollora/async/dispatched action hook#18; degrades gracefully without it).Request contexts
REST and admin-ajax exit before Laravel's
RequestHandled/Terminating: the package sendsphpdebugbar-id(onrest_post_dispatch/admin_init) and collects atshutdown, so the calls appear in the bar's request list.Extension points
Pollora\Debugbar\Collectorbase class (origin, title, widget presets, sections), container tagspollora.debugbar.collectors/pollora.debugbar.sections.pollora/debugbar/registeraction with aRegistry(variables(),table(),section()), pluspollora/debugbar/message|start|stopand Query Monitor'sqm/*actions.Origins are told apart: Pollora tab first,
WP …tabs next, third parties last (orderoption);wp_*andpollora*names reserved.Depends on
AnsweringTemplate,WordPressBooting, discovery scans). CI requires its branch until v13.35.3 is tagged; the step is marked to remove.Tests
61 Pest tests (unit + Testbench feature), PHPStan level 6, Pint.
Draft until checked on a real site (scratch project).