laravel-5

HTTP Controllers 73
.
17 {
18 return view('user.profile', ['user' => User::findOrFail($id)]);
19 }
20 }
We can route to the controller action like so:
.
1 Route::get('user/{id}', 'UserController@showProfile');
Now, when a request matches the specified route URI, the showProfile method on the UserController
class will be executed. Of course, the route parameters will also be passed to the method.
Controllers & Namespaces
It is very important to note that we did not need to specify the full controller namespace when
defining the controller route. We only defined the portion of the class name that comes after
the App\Http\Controllers namespace “root”. By default, the RouteServiceProvider will load the
routes.php file within a route group containing the root controller namespace.
If you choose to nest or organize your controllers using PHP namespaces deeper into the App\Http\Controllers
directory, simply use the specific class name relative to the App\Http\Controllers root namespace.
So, if your full controller class is App\Http\Controllers\Photos\AdminController, you would
register a route like so:
.
1 Route::get('foo', 'Photos\AdminController@method');
Naming Controller Routes
Like Closure routes, you may specify names on controller routes:
.
1 Route::get('foo', ['uses' => 'FooController@method', 'as' => 'name']);
Once you have assigned a name to the controller route, you can easily generate URLs to the action. To
generate a URL to a controller action, use the action helper method. Again, we only need to specify
the part of the controller class name that comes after the base App\Http\Controllers namespace: