Resource controllers in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this resource controller route?

Consider a Laravel resource controller registered as Route::resource('photos', PhotoController::class);. What URL and HTTP method will trigger the edit method of PhotoController?

A PUT /photos/{photo}/edit

B POST /photos/{photo}/edit

C GET /photos/{photo}/edit

D GET /photos/edit/{photo}

💡 Hint

Remember the RESTful conventions for resource controllers in Laravel.

The edit method is accessed via a GET request to /photos/{photo}/edit. This URL shows a form to edit the photo resource.

❓ state_output

intermediate

What is the value of $request->method() in the update method?

In a Laravel resource controller, the update method is called when submitting an edit form. What HTTP method does $request->method() return inside the update method?

A PUT

B PATCH

C GET

D POST

💡 Hint

Laravel uses a special hidden input to spoof HTTP methods in forms.

The update method responds to PUT or PATCH requests. Standard Laravel edit forms use @method('PUT'), so $request->method() returns PUT.

📝 Syntax

advanced

Which option correctly registers a resource controller with only index and show methods?

You want to register a resource controller but only allow the index and show methods. Which route registration is correct?

A Route::resource('posts', PostController::class)->except(['create', 'edit']);

B Route::resource('posts', PostController::class)->filter(['index', 'show']);

C Route::resource('posts', PostController::class)->methods(['index', 'show']);

D Route::resource('posts', PostController::class)->only(['index', 'show']);

💡 Hint

Check Laravel's resource route options for limiting methods.

The only method limits the resource routes to specified methods. except excludes methods but is not the best choice here. methods and filter do not exist.

🔧 Debug

advanced

Why does this resource controller method not receive the model instance?

Given this resource controller method:

public function show(Post $post) { return view('post.show', compact('post')); }

And this route registration:

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

Why might $post be null or cause an error?

A The model class <code>Post</code> does not exist.

B The route parameter name does not match the method parameter name.

C The controller method is missing a return statement.

D The route is missing a middleware for authentication.

💡 Hint

Check the route parameter names and method parameter names for exact match.

Laravel uses route model binding by matching the route parameter name with the method parameter name. If they differ, Laravel cannot inject the model instance.

🧠 Conceptual

expert

What is the main advantage of using resource controllers in Laravel?

Why do developers prefer using resource controllers instead of defining individual routes for each CRUD action?

A They automatically generate all standard CRUD routes with consistent naming and HTTP methods.

B They allow defining routes without any controller methods.

C They disable CSRF protection for all routes automatically.

D They force all routes to use the GET method for simplicity.

💡 Hint

Think about how resource controllers help organize routes and methods.

Resource controllers provide a clean, standardized way to create all CRUD routes with proper HTTP verbs and route names, reducing repetitive code and improving maintainability.

Practice

1. What is the main purpose of a resource controller in Laravel?

easy

A. To create views without a controller

B. To handle database migrations automatically

C. To group all CRUD actions for a resource in one controller

D. To manage user authentication only

Solution

1. Step 1: Understand what resource controllers do

   Resource controllers in Laravel group related actions like create, read, update, and delete (CRUD) for a resource in one controller class.

2. Step 2: Compare options with this definition

   Only To group all CRUD actions for a resource in one controller correctly describes this grouping of CRUD actions. Other options describe unrelated features.

3. Final Answer:

   To group all CRUD actions for a resource in one controller -> Option C

4. Quick Check:

   Resource controller = CRUD grouping [OK]

Hint: Resource controllers group CRUD actions in one place [OK]

Common Mistakes:

• Confusing resource controllers with migrations
• Thinking resource controllers handle views alone
• Assuming resource controllers manage authentication

2. Which of the following is the correct syntax to register a resource controller named PostController for the route /posts?

easy

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

B. Route::controller('posts', PostController::class);

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

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

Solution

1. Step 1: Recall Laravel resource route syntax

   The correct syntax uses Route::resource('uri', ControllerClass::class) to register all resource routes.

2. Step 2: Check each option

   Route::resource('posts', PostController::class); matches the correct syntax. Route::controller('posts', PostController::class); uses controller which is different. Route::get('posts', PostController::resource()); is invalid syntax. Route::resource('PostController', 'posts'); swaps parameters incorrectly.

3. Final Answer:

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

4. Quick Check:

   Resource route syntax = Route::resource(uri, Controller::class) [OK]

Hint: Use Route::resource('uri', Controller::class) to register resource routes [OK]

Common Mistakes:

• Using Route::controller instead of Route::resource
• Swapping URI and controller parameters
• Calling resource() as a method on controller instance

3. Given this resource controller route registration:
Route::resource('photos', PhotoController::class);
Which URL and HTTP method will call the destroy method in PhotoController for photo with ID 5?

medium

A. PUT /photos/5/destroy

B. GET /photos/5/destroy

C. POST /photos/5/delete

D. DELETE /photos/5

Solution

1. Step 1: Recall resource route conventions for destroy

   The destroy method is called with HTTP DELETE on the resource URI with the ID, e.g., DELETE /photos/{id}.

2. Step 2: Match options to this pattern

   DELETE /photos/5 matches DELETE /photos/5. Other options use wrong HTTP methods or incorrect URLs.

3. Final Answer:

   DELETE /photos/5 -> Option D

4. Quick Check:

   Destroy = DELETE /resource/{id} [OK]

Hint: Destroy uses DELETE method on /resource/{id} URL [OK]

Common Mistakes:

• Using GET or POST instead of DELETE for destroy
• Adding extra path segments like /destroy or /delete
• Confusing PUT with DELETE method

4. Consider this route registration:
Route::resource('users', UserController::class);
Which of the following code snippets will cause a runtime error when trying to access the show method?

medium

A. public function show() { return 'User not found'; }

B. public function show(User $user) { return $user; }

C. public function show($id) { return view('user.show', compact('id')); }

D. public function show($id) { return User::findOrFail($id); }

Solution

1. Step 1: Understand show method parameter requirements

   The show method expects either an ID parameter or a model instance via route model binding.

2. Step 2: Analyze each option

   public function show() { return 'User not found'; } has no parameter, so Laravel cannot pass the required ID or model, causing a runtime error. Others have correct parameters.

3. Final Answer:

   public function show() { return 'User not found'; } -> Option A

4. Quick Check:

   Show method must accept ID or model parameter [OK]

Hint: Show method needs parameter for ID or model [OK]

Common Mistakes:

• Omitting parameters in show method
• Using wrong parameter types without binding
• Ignoring route model binding requirements

5. You want to create a resource controller for Product but only want to generate routes for index, show, and store methods. Which is the correct way to register this in routes/web.php?

hard

A. Route::resource('products', ProductController::class)->except(['create', 'edit']);

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

C. Route::resource('products', ProductController::class)->skip(['create', 'edit']);

D. Route::resource('products', ProductController::class)->filter(['index', 'show', 'store']);

Solution

1. Step 1: Recall how to limit resource routes

   Laravel allows limiting routes using the only method with an array of method names.

2. Step 2: Evaluate each option

   A uses except(['create', 'edit']) which excludes only create and edit, leaving index, store, show, update, and destroy. B correctly uses only(['index', 'show', 'store']). C and D use invalid methods skip and filter.

3. Final Answer:

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

4. Quick Check:

   Limit resource routes with only([...]) [OK]

Hint: Use ->only([...]) to limit resource controller routes [OK]

Common Mistakes:

• Using invalid methods like skip or filter
• Confusing only with except
• Not passing array to only method