Optional parameters in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

Laravel

Route::get('/user/{id[1]', function ($id = null) {
    return $id ? "User ID: $id" : 'No ID provided';
});

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

A?

B+

C*

D!

Attempts:

3 left

💡 Hint

Common Mistakes

Using symbols like ! or * which are not valid for optional parameters.

Forgetting to provide a default value in the function parameter.

In Laravel, optional route parameters are marked with a question mark ? after the parameter name.

2fill in blank

medium

Complete the controller method signature to make the parameter 'page' optional with a default value of 1.

Laravel

public function showPage([1] $page = 1) {
    return "Showing page: $page";
}

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

Aarray

Bstring

Cbool

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string type which may cause type errors.

Not specifying a type hint at all.

The parameter type int matches the expected page number and allows a default value.

3fill in blank

hard

Fix the error in the route definition by correctly marking the 'category' parameter as optional.

Laravel

Route::get('/products/{category[1]', function ($category = 'all') {
    return "Category: $category";
});

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

A?

B!

C*

D+

Attempts:

3 left

💡 Hint

Common Mistakes

Using symbols other than question mark for optional parameters.

Not providing a default value in the function.

The question mark ? after the parameter name makes it optional in Laravel routes.

4fill in blank

hard

Fill both blanks to define a route with an optional 'slug' parameter and a default value in the closure.

Laravel

Route::get('/post/{slug[1]', function ($slug [2] 'default-post') {
    return "Post slug: $slug";
});

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

A?

B=

C!

D:

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!' or ':' instead of '?' for optional parameters.

Not assigning a default value in the closure parameter.

The question mark ? marks the parameter optional in the route, and the equals sign = sets the default value in the closure.

5fill in blank

hard

Fill all three blanks to create a controller method with an optional string parameter 'name' defaulting to 'Guest' and return a greeting.

Laravel

public function greet([1] $name [2] 'Guest') {
    return "Hello, [3]!";
}

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

Astring

B=

C$name

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong type hint like int.

Forgetting the default value assignment.

Not using the parameter variable in the return.

The parameter is typed as string, given a default value with =, and the variable $name is used in the return string.

Practice

1. What is the main purpose of optional parameters in Laravel functions or routes?

easy

A. To allow functions or routes to work with or without extra information

B. To force users to always provide all parameters

C. To make parameters required by default

D. To disable parameter validation

Solution

1. Step 1: Understand optional parameters

   Optional parameters let functions or routes accept calls even if some parameters are missing.

2. Step 2: Identify the purpose

   This flexibility means the function or route can work with or without extra info, improving usability.

3. Final Answer:

   To allow functions or routes to work with or without extra information -> Option A

4. Quick Check:

   Optional parameters = flexible input [OK]

Hint: Optional means parameters can be skipped safely [OK]

Common Mistakes:

• Thinking optional means parameters are required
• Confusing optional with disabling validation
• Assuming optional parameters come before required ones

2. Which of the following is the correct way to define an optional parameter in a Laravel route closure?

easy

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

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

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

D. Route::get('/user/{id}', function ($id = null) { return $id; });

Solution

1. Step 1: Check route parameter syntax

   Optional parameters in routes use a question mark after the parameter name: {id?}.

2. Step 2: Check function parameter default

   The function parameter must have a default value, like $id = null, to be optional.

3. Final Answer:

   Route::get('/user/{id?}', function ($id = null) { return $id; }); -> Option B

4. Quick Check:

   Optional param syntax = {id?} + default value [OK]

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

Common Mistakes:

• Omitting the question mark in route parameter
• Not giving a default value in function parameter
• Placing question mark inside braces incorrectly

3. Given this Laravel controller method:

public function show($id, $page = 1) {
    return "ID: $id, Page: $page";
}

What will be the output of show(5)?

medium

A. "ID: 5, Page: "

B. "ID: , Page: 1"

C. Error: Missing argument for $page

D. "ID: 5, Page: 1"

Solution

1. Step 1: Identify parameters and defaults

   The method has a required parameter $id and an optional $page with default 1.

2. Step 2: Call with one argument

   Calling show(5) sets $id=5 and uses default $page=1.

3. Final Answer:

   "ID: 5, Page: 1" -> Option D

4. Quick Check:

   Optional param uses default when missing [OK]

Hint: Optional params use default if not passed [OK]

Common Mistakes:

• Expecting error when optional param is missing
• Assuming optional param is empty string
• Confusing order of parameters

4. Consider this Laravel route definition:

Route::get('/post/{id?}/{comment?}', function ($id = 1, $comment = 'none') {
    return "$id - $comment";
});

What is the error in this code?

medium

A. Function parameters must not have default values

B. Default values cannot be strings

C. Optional parameters must be at the end; $id cannot be optional before $comment

D. Route parameters cannot have question marks

Solution

1. Step 1: Check order of optional parameters

   In Laravel, optional parameters must come after all required ones and be at the end in order.

2. Step 2: Analyze parameter order

   Here, $id is optional before $comment which is also optional, but $id is first. This is allowed only if both are optional and route matches accordingly.

3. Step 3: Identify route matching issue

   Laravel cannot distinguish which parameter is missing if earlier optional parameters are skipped but later ones are present.

4. Final Answer:

   Optional parameters must be at the end; $id cannot be optional before $comment -> Option C

5. Quick Check:

   Optional params order matters [OK]

Hint: Put optional params only at the end [OK]

Common Mistakes:

• Ignoring order of optional parameters
• Thinking default values cannot be strings
• Believing question marks are invalid in routes

5. You want to create a Laravel route that accepts a required category and an optional page number with default 1. Which of these route and controller method pairs is correct?

hard

A. Route::get('/items/{category}/{page?}', [ItemController::class, 'index']);public function index($category, $page = 1) { return "$category - $page"; }

B. Route::get('/items/{category?}/{page}', [ItemController::class, 'index']);public function index($category = 'all', $page) { return "$category - $page"; }

C. Route::get('/items/{category}/{page}', [ItemController::class, 'index']);public function index($category, $page = 1) { return "$category - $page"; }

D. Route::get('/items/{category?}/{page?}', [ItemController::class, 'index']);public function index($category = 'all', $page = 1) { return "$category - $page"; }

Solution

1. Step 1: Identify required and optional parameters in route

   The required parameter category must come first without a question mark. The optional page comes after with a question mark.

2. Step 2: Match controller method parameters

   The method must have $category first (required) and $page second with default 1.

3. Step 3: Check each option

   Route::get('/items/{category}/{page?}', [ItemController::class, 'index']);
   public function index($category, $page = 1) { return "$category - $page"; } matches the correct route and method signature. Others either reverse order or make required params optional incorrectly.

4. Final Answer:

   Option A with required category and optional page correctly defined -> Option A

5. Quick Check:

   Required first, optional after with defaults [OK]

Hint: Required params first, optional with default after [OK]

Common Mistakes:

• Making required params optional in route
• Placing optional params before required ones
• Not giving default values in method