Resource controllers in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to register a resource controller route in Laravel.

Laravel

Route::[1]('photos', PhotoController::class);

Drag options to blanks, or click blank then click option'

Aresource

Bget

Cpost

Dview

Attempts:

3 left

💡 Hint

Common Mistakes

Using get or post instead of resource.

Trying to manually define each route instead of using resource.

Use resource to register all resource routes for a controller in Laravel.

2fill in blank

medium

Complete the method name to show the form for creating a new resource.

Laravel

public function [1]()
{
    return view('photos.create');
}

Drag options to blanks, or click blank then click option'

Acreate

Bedit

Cstore

Dindex

Attempts:

3 left

💡 Hint

Common Mistakes

Using store instead of create for showing the form.

Confusing edit with create.

The create method shows the form to add a new resource.

3fill in blank

hard

Fix the error in the method signature for updating a resource.

Laravel

public function update(Request $request, [1] $photo)
{
    // update logic
}

Drag options to blanks, or click blank then click option'

Aint

BPhoto

Cstring

Darray

Attempts:

3 left

💡 Hint

Common Mistakes

Using int or string instead of the model class.

Not type-hinting the parameter at all.

The update method should type-hint the model class to get the resource instance.

4fill in blank

hard

Fill both blanks to define a route that only includes index and show methods.

Laravel

Route::resource('articles', ArticleController::class)->[1](['[2]', 'show']);

Drag options to blanks, or click blank then click option'

Aonly

Bexcept

Cindex

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using except instead of only.

Putting wrong method names in the array.

Use only to limit resource routes to specific methods like index and show.

5fill in blank

hard

Fill all three blanks to define a resource route with a custom parameter name.

Laravel

Route::resource('users', UserController::class)->parameters(['users' => '[1]']);

public function show([2] $[3])
{
    // show user
}

Drag options to blanks, or click blank then click option'

Amember

BUser

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Not matching the parameter name in the method signature.

Using wrong case for class or variable names.

Use parameters to rename route parameters. The method should type-hint the model class and use the new parameter name.

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