Laravel5.1 Routing - routing packets

What are the benefits of routing packets ？

Sometimes A lot of routes have something in common , For example, they all use a middleware ( Write in two days ) Or the prefix is the same , Avoid code duplication We can divide them into a group .

---

1 Which attributes can be shared by routing packets ？

• middleware middleware.
• The namespace of the controller namespace.
• subdomain domain
• Route prefix

1.1 middleware

About middleware K I haven't written notes about , Let's talk about it briefly Middleware is to verify something after receiving the request or verify something after corresponding , such as Laravel Self contained Auth middleware Is to verify whether the user has logged in , If the user is not logged in , Then it will automatically jump to the login page , We don't need to implement this logic at all .

All right. Return to the right topic , Let's see how to write routing packets ：

/** *  This is a routing packet  /user and /user/profile Will use auth middleware . */ Route::group(['middleware' => 'auth'], function (){ Route::get('/user', function (){ }); Route::get('/user/profile', function (){ }); });

Copy

1.2 Route prefix

/** *  What about the routing prefix   That is to say, all routing paths in this packet are prefixed  */ Route::group(['prefix' => 'admin'], function (){ /** *  Routing packets can be nested  */ Route::group(['middleware' => 'auth'], function (){ /** *  This route not only uses auth middleware , And added admin Prefix , We go through /admin/user Ability to visit  */ Route::get('/user', function (){ }); Route::get('/user/profile', function (){ }); }); /** *  The access path is :/admin */ Route::get('/', function (){ });; });

Copy

1.3 subdomain

/** *  For example, we can input larger To access the route , In the sub route, you can set larger Fetch . */ Route::group(['domain' => '{account}.myapp.com'], function () { Route::get('user/{id}', function ($account, $id) { //  }); });

Copy

Be careful ： If you want to test the subdomain name, you need to use homestand To set your domain name . Be careful ： If you want to test the subdomain name, you need to use homestand To set your domain name .

1.4 Namespace

This is another point that has not been written This contains the contents of the controller , Let's look at the examples first I'll learn the controller tomorrow It's time to take notes .

/** *  As long as the namespace is specified , Then all controllers used in the sub route are located in App\Http\Controller\Admin Under this namespace . */ Route::group(['namespace' => 'Admin', 'prefix' => 'admin'], function(){ /** *  Actually HomeController stay App\Http\Controller\Admin Under this namespace . */ Route::get('/', '[email protected]'); });

Copy

1.5 Group naming

add , In the previous basic article, we learned to name routes , Can the grouping be named ,Yo Man.. Certainly. ：

/** *  Just like normal routing   Also use as But the first letter should be capitalized followed by two colons   It represents a group   If you write like this   We can go through  route('Admin::index') Way to find it  */ Route::group(['namespace' => 'Admin', 'prefix' => 'admin', 'as' => 'Admin::'], function(){ Route::get('/', ['as' => 'index','uses' => '[email protected]']); });

Copy

Publisher ： Full stack programmer stack length , Reprint please indicate the source ：https://javaforall.cn/113173.html Link to the original text ：https://javaforall.cn