Resource routes in Laravel - Step-by-Step Execution

Concept Flow - Resource routes

Define Resource Route

↓

Laravel Maps URLs

↓

Create Controller Methods

↓

Handle HTTP Requests

↓

Return Response

↓

User Sees Result

Resource routes connect URLs to controller methods automatically, handling common actions like list, create, update, and delete.

Execution Sample

Laravel

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

This single line creates multiple routes for posts, linking URLs to PostController methods.

Execution Table

Step	URL	HTTP Method	Controller Method	Action Description
1	/posts	GET	index	Show list of posts
2	/posts/create	GET	create	Show form to create a post
3	/posts	POST	store	Save new post
4	/posts/{post}	GET	show	Show a single post
5	/posts/{post}/edit	GET	edit	Show form to edit post
6	/posts/{post}	PUT/PATCH	update	Update existing post
7	/posts/{post}	DELETE	destroy	Delete a post
8	-	-	-	No more routes, resource routes complete

💡 All 7 resource routes are registered, covering standard CRUD actions.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Registered Routes	[]	[GET /posts]	[GET /posts, GET /posts/create]	[GET /posts, GET /posts/create, POST /posts]	[GET /posts, GET /posts/create, POST /posts, GET /posts/{post}]	[GET /posts, GET /posts/create, POST /posts, GET /posts/{post}, GET /posts/{post}/edit]	[GET /posts, GET /posts/create, POST /posts, GET /posts/{post}, GET /posts/{post}/edit, PUT/PATCH /posts/{post}]	[GET /posts, GET /posts/create, POST /posts, GET /posts/{post}, GET /posts/{post}/edit, PUT/PATCH /posts/{post}, DELETE /posts/{post}]

Key Moments - 3 Insights

Why does one Route::resource line create many URLs?

Because Laravel automatically maps standard CRUD URLs to controller methods as shown in the execution_table steps 1 to 7.

What HTTP method is used to update a post?

PUT or PATCH is used to update, as shown in step 6 of the execution_table.

How does Laravel know which controller method to call for /posts/5/edit?

It matches the URL pattern /posts/{post}/edit and calls the 'edit' method, as shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, which controller method handles the URL '/posts' with GET?

A index

B show

C store

D edit

💡 Hint

Check step 1 in the execution_table for URL '/posts' with GET method.

At which step does Laravel register the route to delete a post?

A Step 4

B Step 3

C Step 7

D Step 6

💡 Hint

Look for the DELETE HTTP method in the execution_table.

If you add Route::resource('comments', CommentController::class), how does the variable 'Registered Routes' change after step 8?

A It replaces all post routes with comment routes

B It adds 7 new routes for comments

C It adds only one new route for comments

D It does not change

💡 Hint

Resource routes always add 7 routes per resource as shown in variable_tracker.

Concept Snapshot

Resource routes in Laravel map standard URLs to controller methods automatically.
Use Route::resource('name', Controller::class) to create 7 routes.
These routes cover index, create, store, show, edit, update, destroy.
Each route uses specific HTTP methods and URL patterns.
This saves time and keeps routing organized.

Full Transcript

Resource routes in Laravel let you create many routes with one line. When you write Route::resource('posts', PostController::class), Laravel creates 7 routes for you. These routes handle showing all posts, showing a form to create a post, saving a new post, showing one post, editing a post, updating a post, and deleting a post. Each route uses a specific URL and HTTP method. For example, GET /posts calls the index method to list posts. DELETE /posts/{post} calls the destroy method to delete a post. This automatic mapping helps you write less code and keep your app organized.

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