Hi, thanks for the great rewrite of this package!
We're migrating an app from an older Phalcon-community debug bar (based on maximebf/php-debugbar, which supported storing collected data across requests and browsing previous ones via an "open handler" - useful for inspecting AJAX calls, redirects, or a request that already finished before you could look at the bar).
Looking through the source of phalcon/debugbar v0.4.0, it seems the bar only ever reflects the current request (rendered inline via the application:beforeSendResponse listener), with no storage/persistence layer or history navigation.
Is this feature on the roadmap, or intentionally out of scope for this package's design? If there's a recommended pattern to achieve something similar (e.g. persisting collector data to a storage backend and exposing an endpoint to browse it), a pointer would be very helpful. Happy to contribute if there's interest and a rough direction is agreed on.
Thanks!
Hi, thanks for the great rewrite of this package!
We're migrating an app from an older Phalcon-community debug bar (based on maximebf/php-debugbar, which supported storing collected data across requests and browsing previous ones via an "open handler" - useful for inspecting AJAX calls, redirects, or a request that already finished before you could look at the bar).
Looking through the source of phalcon/debugbar v0.4.0, it seems the bar only ever reflects the current request (rendered inline via the application:beforeSendResponse listener), with no storage/persistence layer or history navigation.
Is this feature on the roadmap, or intentionally out of scope for this package's design? If there's a recommended pattern to achieve something similar (e.g. persisting collector data to a storage backend and exposing an endpoint to browse it), a pointer would be very helpful. Happy to contribute if there's interest and a rough direction is agreed on.
Thanks!