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
2 changed files with 4 additions and 3 deletions

View File

@@ -48,7 +48,8 @@ Route::get('/', function()
|
| Similarly, we use an event to handle the display of 500 level errors
| 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 @@ Event::listen('404', function()
return Response::error('404');
});
Event::listen('500', function()
Event::listen('500', function($exception)
{
return Response::error('500');
});

View File

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