Laravel Starter - PHP User Group (Myanmar)

Laravel Starter
Let's take a look:
Route::filter('auth', function()
{
if (Auth::guest()) return Redirect::to('login');
});
You can see that a filter is registered with the Route::filter() method. The typical location
to store filter registrations is within your application/routes.php file.
The Route::filter() method takes two parameters. The first is a string containing the name
of the filter. The second is the anonymous function that will be run when the filter is activated.
In this example, the anonymous function will check if a user is logged in using the
Auth::guest() method. If the user is not logged in, the filter returns a response object that
tells Laravel to redirect the user to the login page.
It's important to note that while you can return response objects from before filters, it's not
possible to redirect from after filters as at this point it's too late.
Now that we have the auth filter, how do we tell Laravel when to run it? The correct algorithm
is situational.
The following is an example of applying a filter to a routed function:
Route::get('admin', array('before' => 'auth', function()
{
return View::make('admin.dashboard');
}));
In this example, we want to provide an admin dashboard for users who have successfully
authenticated. You may notice that our Route::get() declaration has changed. Our first
argument is still the route's URI. However, our second argument is no longer an anonymous
function, it's now an array. This array provides a method for configuring our route registration.
Laravel knows that when you pass a key/value pair, it should be used as configuration and that
when you pass an anonymous function, it should be used as the target function for the route.
39