Resource routes in Laravel

Introduction

Resource routes help you quickly create all the common routes for a controller in one line. This saves time and keeps your code clean.

When you have a controller managing a resource like users, posts, or products.

When you want to follow RESTful conventions for your web app routes.

When you want to avoid writing each route manually for actions like create, read, update, and delete.

When you want Laravel to automatically handle route naming and HTTP methods for you.

Syntax

Laravel

Route::resource('resource-name', ControllerName::class);

This single line creates multiple routes for standard actions.

The 'resource-name' is the URL segment, and the controller handles the logic.

Examples

Creates routes for posts with PostController handling actions.

Laravel

Route::resource('posts', PostController::class);

Creates all user-related routes like index, show, create, edit, update, and delete.

Laravel

Route::resource('users', UserController::class);

Creates only the index and show routes for products.

Laravel

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

Creates all routes except the destroy (delete) route for orders.

Laravel

Route::resource('orders', OrderController::class)->except(['destroy']);

Sample Program

This code creates all standard routes for managing books. Laravel will map URLs like /books, /books/create, /books/{book}, etc., to the correct methods in BookController.

Laravel

<?php

use Illuminate\Support\Facades\Route;
use App\Http\Controllers\BookController;

Route::resource('books', BookController::class);

// BookController should have methods: index, create, store, show, edit, update, destroy

Important Notes

Resource routes follow RESTful URL and HTTP method conventions automatically.

You can customize which routes to create using only() or except() methods.

Make sure your controller has the matching methods for the routes to work properly.

Summary

Resource routes create many routes in one line for common actions.

They follow RESTful patterns for URLs and HTTP methods.

Use only() or except() to control which routes are generated.

Practice

1. What does the Route::resource('photos', PhotoController::class) method do in Laravel?

easy

A. Creates multiple routes for common CRUD actions automatically.

B. Creates a single route for the index method only.

C. Creates routes only for the create and edit methods.

D. Deletes all existing routes related to photos.

Solution

1. Step 1: Understand the purpose of Route::resource

   This method generates routes for all standard CRUD actions (index, create, store, show, edit, update, destroy) automatically.

2. Step 2: Recognize the effect on routes

   It saves time by creating multiple routes with correct HTTP verbs and URLs for the resource controller.

3. Final Answer:

   Creates multiple routes for common CRUD actions automatically. -> Option A

4. Quick Check:

   Resource routes = multiple CRUD routes [OK]

Hint: Resource routes generate all CRUD URLs in one line [OK]

Common Mistakes:

• Thinking it creates only one route
• Confusing resource with single route methods
• Assuming it deletes routes

2. Which of the following is the correct syntax to create resource routes for a controller named PostController?

easy

A. Route::resource('posts', 'PostController::class');

B. Route::resource('posts', 'PostController');

C. Route::resource('posts', PostController);

D. Route::resource('posts', PostController::class);

Solution

1. Step 1: Identify correct controller reference syntax

   In Laravel, the controller class should be passed using the ::class constant without quotes.

2. Step 2: Check each option

   Route::resource('posts', PostController::class); correctly uses PostController::class without quotes, which is the modern and recommended syntax.

3. Final Answer:

   Route::resource('posts', PostController::class); -> Option D

4. Quick Check:

   Use ControllerName::class without quotes [OK]

Hint: Use ControllerName::class without quotes for resource routes [OK]

Common Mistakes:

• Passing controller name as a string with quotes
• Omitting ::class
• Using quotes around ::class

3. Given the route definition Route::resource('books', BookController::class)->only(['index', 'show']);, which URLs will be available?

medium

A. /books/create (GET) and /books/{book}/edit (GET)

B. /books (GET) and /books/{book} (GET)

C. /books (POST) and /books/{book} (DELETE)

D. /books/{book} (PUT) and /books/{book} (PATCH)

Solution

1. Step 1: Understand the only() method

   The only() method limits resource routes to specified actions. Here, only 'index' and 'show' routes are created.

2. Step 2: Identify routes for index and show

   Index route is GET /books, show route is GET /books/{book}.

3. Final Answer:

   /books (GET) and /books/{book} (GET) -> Option B

4. Quick Check:

   only(['index','show']) = GET /books and GET /books/{id} [OK]

Hint: only(['index','show']) creates just list and detail GET routes [OK]

Common Mistakes:

• Confusing HTTP verbs for actions
• Assuming create/edit routes are included
• Mixing POST or DELETE with index/show

4. What is wrong with this route definition?

Route::resource('users', UserController::class)->except('store');

medium

A. The except() method requires an array, not a string.

B. UserController::class should be a string.

C. Resource routes cannot use except() method.

D. The route name 'users' is invalid.

Solution

1. Step 1: Check except() method usage

   The except() method expects an array of action names to exclude, not a single string.

2. Step 2: Identify correct syntax

   It should be except(['store']) with square brackets to pass an array.

3. Final Answer:

   The except() method requires an array, not a string. -> Option A

4. Quick Check:

   Use except(['action']) with array brackets [OK]

Hint: Pass array to except(), not a single string [OK]

Common Mistakes:

• Passing string instead of array to except()
• Using quotes incorrectly around controller class
• Thinking except() is not allowed

5. You want to create resource routes for ArticleController but only allow routes for creating, storing, and editing articles. Which is the correct route definition?

hard

A. Route::resource('articles', ArticleController::class)->only(['create', 'store', 'edit']);

B. Route::resource('articles', ArticleController::class)->only(['create', 'edit']);

C. Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']);

D. Route::resource('articles', ArticleController::class)->except(['store']);

Solution

1. Step 1: Identify required actions

   We want routes for create, store, and edit only.

2. Step 2: Use except() to exclude unwanted actions

   Excluding index, show, update, and destroy leaves only create, store, and edit routes.

3. Step 3: Confirm only() option

   Route::resource('articles', ArticleController::class)->only(['create', 'store', 'edit']); correctly includes the store route, but using except() as in Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']); is also correct and often preferred for excluding unwanted routes.

4. Final Answer:

   Route::resource('articles', ArticleController::class)->except(['index', 'show', 'update', 'destroy']); -> Option C

5. Quick Check:

   except(['index','show','update','destroy']) = create, store, edit routes [OK]

Hint: Use except() to exclude unwanted routes for precise control [OK]

Common Mistakes:

• Using only() but missing store route
• Excluding wrong actions
• Confusing create and store routes