laravel-5

Upgrade Guide 31
Events
Core Event Objects
Some of the core events fired by Laravel now use event objects instead of string event names and
dynamic parameters. Below is a list of the old event names and their new object based counterparts:
Old | New ————- | ————- artisan.start | Illuminate\Console\Events\ArtisanStarting
auth.attempting | Illuminate\Auth\Events\Attempting auth.login | Illuminate\Auth\Events\Login
auth.logout | Illuminate\Auth\Events\Logout cache.missed | Illuminate\Cache\Events\CacheMissed
cache.hit | Illuminate\Cache\Events\CacheHit cache.write | Illuminate\Cache\Events\KeyWritten
cache.delete | Illuminate\Cache\Events\KeyForgotten connection.{name}.beginTransaction
| Illuminate\Database\Events\TransactionBeginning connection.{name}.committed | Illuminate\Database\Events\TransactionCommitted
connection.{name}.rollingBack | Illuminate\Database\Events
illuminate.query | Illuminate\Database\Events\QueryExecuted illuminate.queue.before | Illuminate\Queue\Events\JobProcessing
illuminate.queue.after | Illuminate\Queue\Events\JobProcessed
illuminate.queue.failed | Illuminate\Queue\Events\JobFailed illuminate.queue.stopping |
Illuminate\Queue\Events\WorkerStopping mailer.sending | Illuminate\Mail\Events\MessageSending
router.matched | Illuminate\Routing\Events\RouteMatched
Each of these event objects contains exactly the same parameters that were passed to the event
handler in Laravel 5.1. For example, if you were using DB::listen in 5.1., you may update your code
like so for 5.2.:
1 DB::listen(function ($event) {
2 dump($event->sql);
3 dump($event->bindings);
4 });
You may check out each of the new event object classes to see their public properties.
Exception Handling
Your App\Exceptions\Handler class’ $dontReport property should be updated to include at least
the following exception types: