-
-
Notifications
You must be signed in to change notification settings - Fork 220
Debugger::$disableHandlers, Pjax support #334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ad 1) When you disable Tracy's handlers, what is the purpose of Tracy then? You don't need it enabled after all. ad 2) It is non systematic solution. You can detect |
|
The concept/need behind this seems somewhat similar to this: #279 I still have to modify the Tracy core on each update to include those changes. I think it wouldn't bet great to have some flexibility to override various handlers. |
You can overload exception handler after Tracy is enabled. Tracy\Debugger::enable(...);
$prev = null;
$prev = set_exception_handler(function (...) use (&$prev) {
...
if ($prev) $prev(...func_get_args());
}); and the same for error handler: set_error_handler(function (...) {
...
return false; # Call previous one
}); I just want to say, that PHP has already API for it.
So why the requests looks like AJAX when they are not? Isn't Pjax library issue? You can always modify |
729637b
to
c458b58
Compare
c086066
to
d52afaa
Compare
342ef20
to
6d06dc1
Compare
55360f2
to
867c2b6
Compare
a2951f1
to
1116024
Compare
$disableHandlers allows to disable register_shutdown_handlers() and set_exception_handler() and use your own handlers.
Pjax support (https://github.com/defunkt/jquery-pjax). We treat Pjax requests not like regular Ajax requests.