Route groups in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a route group in Laravel?

A route group lets you share common attributes like middleware, prefix, or namespace across multiple routes to keep your code clean and organized.

beginner

How do you add a URL prefix to all routes in a group?

Use the 'prefix' key in the group array. For example: Route::prefix('admin')->group(function () { ... }); adds 'admin/' before all routes inside.

intermediate

What is the benefit of applying middleware in a route group?

Applying middleware in a group means all routes inside share the same middleware, so you don't repeat middleware on each route individually.

intermediate

Show a simple example of a route group with a prefix and middleware.

Route::middleware('auth')->prefix('dashboard')->group(function () { Route::get('/stats', [StatsController::class, 'index']); Route::get('/profile', [ProfileController::class, 'show']); }); This groups routes under '/dashboard' and applies 'auth' middleware.

advanced

Can route groups be nested in Laravel? What is the use?

Yes, route groups can be nested. This helps combine multiple shared attributes like prefix and middleware in layers, making complex route structures easier to manage.

Which of the following is NOT a common attribute you can share in a Laravel route group?

A controller method

B prefix

C middleware

D namespace

Controller methods are defined per route, not shared in route groups. Middleware, prefix, and namespace can be shared.

How do you start a route group with a middleware named 'auth'?

A Route::group(['middleware' => 'auth'], function () { ... });

B Route::middleware('auth')->group(function () { ... });

C Route::prefix('auth')->group(function () { ... });

D Both A and D

Both ways are valid to apply middleware 'auth' to a route group.

What will be the full URL for this route inside a group with prefix 'admin'? Route::get('/users', ...);

A /admin/users

B /users

C /admin

D /users/admin

The prefix 'admin' is added before the route path, so the full URL is '/admin/users'.

Can you nest route groups in Laravel?

A No, nesting is not allowed

B Yes, to combine multiple shared attributes

C Only if they share the same prefix

D Only if they share the same middleware

Nesting route groups is allowed and useful to combine different shared attributes like prefix and middleware.

Which method is used to define a route group in Laravel?

A Route::makeGroup()

B Route::setGroup()

C Route::group()

D Route::createGroup()

The correct method to define a route group is Route::group().

Explain how route groups help organize routes in Laravel and give an example with a prefix and middleware.

Think about how you can avoid repeating code for multiple routes.

Describe nesting route groups and why it might be useful in a Laravel application.

Consider when you want to apply multiple layers of prefixes or middleware.

Practice

1. What is the main purpose of using Route::group() in Laravel?

easy

A. To register routes only for API requests

B. To define a single route with multiple HTTP methods

C. To create a route that redirects to another URL

D. To apply shared settings like middleware or prefixes to multiple routes at once

Solution

1. Step 1: Understand Route Group Purpose

   Route groups allow you to bundle routes that share common attributes like middleware or URL prefixes.

2. Step 2: Compare with Other Options

   Options A, B, and C describe different routing features, not the grouping concept.

3. Final Answer:

   To apply shared settings like middleware or prefixes to multiple routes at once -> Option D

4. Quick Check:

   Route groups = shared settings [OK]

Hint: Route groups bundle routes with common settings fast [OK]

Common Mistakes:

• Thinking route groups define single routes
• Confusing route groups with route redirects
• Assuming route groups are only for API routes

2. Which of the following is the correct syntax to create a route group with a prefix admin in Laravel?

easy

A. Route::group('prefix' => 'admin', function () { /* routes */ });

B. Route::group(['prefix' => 'admin'], function () { /* routes */ });

C. Route::group(['admin' => 'prefix'], function () { /* routes */ });

D. Route::group(function () { prefix('admin'); /* routes */ });

Solution

1. Step 1: Recall Route Group Syntax

   Route groups use an array of attributes as the first argument, e.g., ['prefix' => 'admin'].

2. Step 2: Identify Correct Array Syntax

   Route::group(['prefix' => 'admin'], function () { /* routes */ }); correctly uses the array with 'prefix' key and a closure function.

3. Final Answer:

   Route::group(['prefix' => 'admin'], function () { /* routes */ }); -> Option B

4. Quick Check:

   Array with 'prefix' key = correct syntax [OK]

Hint: Use array with 'prefix' key inside Route::group [OK]

Common Mistakes:

• Missing array brackets around attributes
• Swapping key and value in array
• Trying to call prefix() inside the closure

3. Given the following route group code, what URL will respond to the Route::get('dashboard', ...) route?

Route::group(['prefix' => 'admin'], function () {
    Route::get('dashboard', function () {
        return 'Admin Dashboard';
    });
});

medium

A. /admin/dashboard

B. /admin

C. /dashboard

D. /dashboard/admin

Solution

1. Step 1: Understand Prefix Effect

   The 'prefix' => 'admin' adds '/admin' before all routes inside the group.

2. Step 2: Combine Prefix and Route URI

   The route URI is 'dashboard', so combined URL is '/admin/dashboard'.

3. Final Answer:

   /admin/dashboard -> Option A

4. Quick Check:

   Prefix + route URI = /admin/dashboard [OK]

Hint: Prefix adds before route URI in URL [OK]

Common Mistakes:

• Ignoring the prefix and using only route URI
• Appending prefix after route URI
• Confusing route name with URL

4. Identify the error in this route group code:

Route::group(['middleware' => 'auth'], function {
    Route::get('profile', function () {
        return 'User Profile';
    });
});

medium

A. Missing parentheses after function keyword

B. Middleware should be an array, not a string

C. Route::group cannot use middleware

D. Route URI 'profile' is invalid

Solution

1. Step 1: Check Closure Syntax

   The anonymous function must have parentheses: function() { ... }.

2. Step 2: Validate Middleware Usage

   Middleware can be a string or array, so that is correct here.

3. Final Answer:

   Missing parentheses after function keyword -> Option A

4. Quick Check:

   Anonymous function needs () after function [OK]

Hint: Always add () after function keyword for closures [OK]

Common Mistakes:

• Omitting parentheses in anonymous functions
• Thinking middleware must be array always
• Assuming route URI 'profile' is invalid

5. You want to create a route group with prefix api and middleware auth:api. Inside it, you define a route GET /users that returns a JSON list of users. Which is the correct way to write this in Laravel?

hard

A. Route::middleware('auth:api')->group(['prefix' => 'api'], function () {
Route::get('users', function () {
return response()->json(['users' => []]);
});
});

B. Route::group(['prefix' => 'api'], function () {
Route::middleware('auth:api')->get('users', function () {
return ['users' => []];
});
});

C. Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () {
Route::get('users', function () {
return response()->json(['users' => []]);
});
});

D. Route::group(['middleware' => 'auth:api'], function () {
Route::prefix('api')->get('users', function () {
return response()->json(['users' => []]);
});
});

Solution

1. Step 1: Combine Prefix and Middleware in One Group

   Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); correctly passes both 'prefix' and 'middleware' as keys in the attributes array.

2. Step 2: Check Route Definition Inside Group

   The route uses Route::get with URI 'users' and returns JSON response properly.

3. Step 3: Verify Other Options

   Route::group(['prefix' => 'api'], function () { Route::middleware('auth:api')->get('users', function () { return ['users' => []]; }); }); applies middleware only to the route, not the group prefix. Route::middleware('auth:api')->group(['prefix' => 'api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); has wrong group syntax. Route::group(['middleware' => 'auth:api'], function () { Route::prefix('api')->get('users', function () { return response()->json(['users' => []]); }); }); misuses prefix inside the route.

4. Final Answer:

   Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); -> Option C

5. Quick Check:

   Group attributes array with prefix and middleware [OK]

Hint: Put prefix and middleware together in group attributes array [OK]

Common Mistakes:

• Splitting prefix and middleware into separate calls incorrectly
• Misplacing prefix() inside route closure
• Using middleware() outside group incorrectly