Annajwaszahro
/
MIF_E31222691
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #1711 from torm3nt/master 

Event firing of 500s now passes along the $exception object
This commit is contained in:
Taylor Otwell 2013-03-28 14:28:04 -07:00
parent 3f803d4eb3 bc36205a99
commit 7fe61b74d6
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
application/routes.php
View File

@ -48,7 +48,8 @@
| |
| Similarly, we use an event to handle the display of 500 level errors | Similarly, we use an event to handle the display of 500 level errors
| within the application. These errors are fired when there is an | within the application. These errors are fired when there is an
| uncaught exception thrown in the application. | uncaught exception thrown in the application. The exception object
| that is captured during execution is then passed to the 500 listener.
| |
*/ */
@ -57,7 +58,7 @@
return Response::error('404'); return Response::error('404');
}); });
Event::listen('500', function() Event::listen('500', function($exception)
{ {
return Response::error('500'); return Response::error('500');
}); });

2
laravel/error.php
View File

@ -54,7 +54,7 @@ public static function exception($exception, $trace = true)
// Using events gives the developer more freedom. // Using events gives the developer more freedom.
else else
{ {
$response = Event::first('500'); $response = Event::first('500', $exception);
$response = Response::prepare($response); $response = Response::prepare($response);
} }