Route parameters in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a route with a required parameter named 'id'.

Laravel

Route::get('/user/[1]', function ($id) {
    return 'User '.$id;
});

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

A<id>

B[id]

C(id)

D{id}

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets or parentheses instead of curly braces.

Forgetting to wrap the parameter name in any brackets.

In Laravel, route parameters are defined using curly braces like {id}.

2fill in blank

medium

Complete the code to define an optional route parameter named 'name'.

Laravel

Route::get('/user/{id}/profile/[1]', function ($id, $name = null) {
    return $name ? "Profile of $name" : "Profile of user $id";
});

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

A{name?}

B{name}

C[name]

D(name?)

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets or parentheses instead of curly braces with question mark.

Forgetting the question mark to mark the parameter optional.

Optional parameters in Laravel routes are defined by adding a question mark inside the curly braces, like {name?}.

3fill in blank

hard

Fix the error in the route definition to correctly capture the 'postId' parameter.

Laravel

Route::get('/posts/[1]', function ($postId) {
    return "Post ID: $postId";
});

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

A<postId>

B[postId]

C{postId}

D(postId)

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets or angle brackets instead of curly braces.

Not wrapping the parameter name at all.

Route parameters must be enclosed in curly braces like {postId} to be captured correctly.

4fill in blank

hard

Fill both blanks to define a route with two parameters: 'category' and optional 'item'.

Laravel

Route::get('/shop/[1]/[2]', function ($category, $item = null) {
    return $item ? "Category: $category, Item: $item" : "Category: $category";
});

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

A{category}

B[item]

C{item?}

D(item)

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets for parameters instead of curly braces.

Not adding the question mark for the optional parameter.

The first parameter is required and uses {category}. The second is optional and uses {item?}.

5fill in blank

hard

Fill all three blanks to create a route with parameters 'year', optional 'month', and optional 'day'.

Laravel

Route::get('/archive/[1]/[2]/[3]', function ($year, $month = null, $day = null) {
    return "Archive for $year" . ($month ? ", month $month" : '') . ($day ? ", day $day" : '');
});

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

A{year}

B{month?}

C{day?}

D[day]

Attempts:

3 left

💡 Hint

Common Mistakes

Using square brackets for optional parameters.

Forgetting question marks for optional parameters.

Required parameter {year} first, then optional {month?} and {day?} with question marks.

Practice

1. What is the purpose of route parameters in Laravel?

easy

A. To define middleware for routes

B. To capture dynamic values from the URL

C. To set HTTP methods for routes

D. To create static pages only

Solution

1. Step 1: Understand route parameters

   Route parameters are placeholders in the URL that capture dynamic values.

2. Step 2: Identify their use

   They allow the app to receive values from the URL to use in controllers or views.

3. Final Answer:

   To capture dynamic values from the URL -> Option B

4. Quick Check:

   Route parameters = dynamic URL values [OK]

Hint: Route parameters capture values inside {} in URLs [OK]

Common Mistakes:

• Confusing parameters with middleware
• Thinking parameters set HTTP methods
• Assuming parameters create static pages

2. Which of the following is the correct syntax to define a required route parameter named id in Laravel?

easy

A. Route::get('/user/{id}', function ($id) {});

B. Route::get('/user/:id', function ($id) {});

C. Route::get('/user/[id]', function ($id) {});

D. Route::get('/user/<id>', function ($id) {});

Solution

1. Step 1: Recall Laravel route parameter syntax

   Laravel uses curly braces {} to define route parameters.

2. Step 2: Match syntax with options

   Only Route::get('/user/{id}', function ($id) {}); uses curly braces correctly: '/user/{id}'.

3. Final Answer:

   Route::get('/user/{id}', function ($id) {}); -> Option A

4. Quick Check:

   Curly braces = route parameters [OK]

Hint: Use curly braces {} for parameters in routes [OK]

Common Mistakes:

• Using colon : instead of curly braces
• Using square brackets [] or angle brackets <>
• Forgetting to pass parameter to callback

3. Given the route definition Route::get('/post/{postId}', function ($postId) { return 'Post ID: ' . $postId; });, what will be the output when visiting /post/42?

medium

A. Post ID:

B. Post ID: {postId}

C. Post ID: 42

D. Error: Missing parameter

Solution

1. Step 1: Understand parameter passing

   The URL segment '42' matches the {postId} parameter and is passed to the function as $postId.

2. Step 2: Evaluate the return statement

   The function returns 'Post ID: ' concatenated with the value of $postId, which is '42'.

3. Final Answer:

   Post ID: 42 -> Option C

4. Quick Check:

   URL value passed to parameter = output [OK]

Hint: URL value replaces parameter in function automatically [OK]

Common Mistakes:

• Expecting literal {postId} in output
• Thinking parameter is optional by default
• Forgetting to concatenate parameter value

4. What is wrong with this route definition? Route::get('/product/{id?}', function () { return 'Product ID: ' . $id; });

medium

A. The parameter $id is missing in the function signature

B. Optional parameters cannot be used in routes

C. Curly braces should be replaced with parentheses

D. Route URL should not contain parameters

Solution

1. Step 1: Check function parameters

   The route URL defines an optional parameter {id?}, but the function does not accept $id as an argument.

2. Step 2: Understand parameter passing

   Laravel passes route parameters to the function, so $id must be declared to use it.

3. Final Answer:

   The parameter $id is missing in the function signature -> Option A

4. Quick Check:

   Function must accept route parameters [OK]

Hint: Function must list all route parameters as arguments [OK]

Common Mistakes:

• Omitting parameters in function
• Thinking optional parameters are disallowed
• Using wrong syntax for optional parameters

5. How can you define a route with an optional parameter category that defaults to 'all' if not provided, and use it inside the route callback?

hard

A. Route::get('/items/{category?}', function ($category) { return 'Category: ' . $category; });

B. Route::get('/items/{category}', function () { return 'Category: all'; });

C. Route::get('/items', function ($category = 'all') { return 'Category: ' . $category; });

D. Route::get('/items/{category?}', function ($category = 'all') { return 'Category: ' . $category; });

Solution

1. Step 1: Define optional parameter in route

   Use curly braces with a question mark {category?} to make the parameter optional.

2. Step 2: Set default value in function

   Assign a default value 'all' to $category in the function signature to handle missing parameter.

3. Final Answer:

   Route::get('/items/{category?}', function ($category = 'all') { return 'Category: ' . $category; }); -> Option D

4. Quick Check:

   Optional parameter + default value = Route::get('/items/{category?}', function ($category = 'all') { return 'Category: ' . $category; }); [OK]

Hint: Use {param?} and default value in function for optional params [OK]

Common Mistakes:

• Not setting default value in function
• Omitting ? in route parameter
• Defining parameter but not using it