Laravel的資源路由通過一行代碼自動(dòng)生成七種CRUD操作對(duì)應(yīng)的路由。當(dāng)你使用Route::resource('photos', PhotoController::class);時(shí)，Laravel會(huì)創(chuàng)建index、create、store、show、edit、update和destroy七個(gè)路由，分別對(duì)應(yīng)控制器中的方法，並基於資源名生成URI。你也可以使用only或except方法指定生成的路由，例如僅保留index和show，或排除create和store；還可以通過parameters方法更改默認(rèn)參數(shù)名稱，如將{photo}改為{my_photo}。在控制器中，應(yīng)遵循命名規(guī)範(fàn)的方法處理邏輯，在視圖中則推薦使用route()函數(shù)配合命名路由生成鏈接或表單，從而提升應(yīng)用靈活性與可維護(hù)性。

When you're working with Laravel and dealing with routes, the resource route is one of the most efficient tools for quickly setting up standard CRUD operations. It automatically maps HTTP methods to controller methods, saving you from manually defining each route. The real power comes when you understand how to use it effectively without getting tripped up by its defaults.

What Does a Resource Route Do?

When you define a route like this:

 Route::resource('photos', PhotoController::class);

Laravel creates seven routes for handling CRUD operations: index , create , store , show , edit , update , and destroy . These correspond to the usual controller methods, and the URIs are based on the resource name you provide.

For example, the edit method for the PhotoController will be mapped to /photos/{photo}/edit and expect a GET request. Each of these routes also maps to a named route, like photos.edit , which is super useful when generating URLs or redirects in your views or controllers.

Customizing the Resource Routes

Sometimes you don't need all seven routes — maybe your app doesn't have an "edit" form, or you want to exclude delete functionality. Laravel lets you control which routes are generated using the only or except methods:

 Route::resource('photos', PhotoController::class)->only([
    'index', 'show'
]);

Route::resource('photos', PhotoController::class)->except([
    'create', 'store'
]);

This helps keep your route list clean and secure by not exposing unnecessary endpoints.

Another thing you might want to customize is the parameter name used in the route. By default, Laravel uses the singular version of the resource name (like {photo} for photos ). If you want to change that:

 Route::resource('photos', PhotoController::class)->parameters([
    'photo' => 'my_photo'
]);

Now your routes will use {my_photo} instead of {photo} in the URLs.

How to Use Resource Routes in Controllers and Views

Once your routes are set up, your controller should follow the expected method names:

• index() – Show a list of resources
• create() – Show the form to create a new resource
• store(Request $request) – Save the new resource
• show($id) – Display a specific resource
• edit($id) – Show the form to edit a resource
• update(Request $request, $id) – Save the updated resource
• destroy($id) – Delete the resource

In your views, especially when generating links or forms, always use the named routes. For example:

 <a href="{{ route(&#39;photos.edit&#39;, $photo->id) }}">Edit Photo</a>

Or for forms:

 <form action="{{ route(&#39;photos.destroy&#39;, $photo->id) }}" method="POST">
    @csrf
    @method(&#39;DELETE&#39;)
    <button type="submit">Delete</button>
</form>

Using named routes ensures your app remains flexible even if the URL structure changes later.

That's basically how the resource route works in Laravel. It's straightforward once you understand what it generates and how to tweak it. The key is knowing when to stick with the defaults and when to customize based on your app's needs.

以上是使用Laravel中的'資源”路線。的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！