Optional parameters in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Laravel handle optional route parameters?

Consider this Laravel route definition:

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

What will be the output when you visit /user URL?

Laravel

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

A It returns null because the default value is null.

B It throws a 404 error because the parameter is missing.

C It returns 'guest' because the parameter is optional and not provided.

D It returns an empty string because no parameter was passed.

💡 Hint

Think about what happens when an optional parameter is not given in the URL.

Laravel allows optional route parameters by adding a question mark ?. If the parameter is missing, the default value in the function is used. Here, $id defaults to null, so the null coalescing operator ?? returns 'guest'.

📝 Syntax

intermediate

Which route definition correctly uses an optional parameter with a default value?

Choose the correct Laravel route definition that sets an optional parameter page with a default value of 1.

A Route::get('/posts/{page?}', function ($page = 1) { return $page; });

B Route::get('/posts/{page}', function ($page = 1) { return $page; });

C Route::get('/posts/{page?}', function ($page) { return $page ?? 1; });

D Route::get('/posts/{page?}', function ($page = null) { return $page; });

💡 Hint

Remember that optional parameters must have a question mark in the route and a default value in the function.

Option A correctly marks the route parameter as optional with {page?} and sets a default value $page = 1 in the closure. Option A is missing the question mark, so the parameter is required. Option A does not set a default value in the function signature. Option A sets default to null but does not provide the default 1.

❓ state_output

advanced

What is the output of this controller method with optional parameters?

Given this Laravel controller method:

public function show($category = 'all', $page = 1) {
    return "Category: $category, Page: $page";
}

If the route is defined as Route::get('/items/{category?}/{page?}', [ItemController::class, 'show']); and the URL /items/books is visited, what is the output?

Laravel

public function show($category = 'all', $page = 1) {
    return "Category: $category, Page: $page";
}

A Category: all, Page: books

B Category: books, Page: 1

C Category: all, Page: 1

D Category: books, Page: books

💡 Hint

Think about how Laravel matches optional parameters in order.

When visiting /items/books, Laravel assigns 'books' to the first optional parameter $category. Since $page is not provided, it uses the default value 1. So the output is 'Category: books, Page: 1'.

🔧 Debug

advanced

Why does this Laravel route with optional parameters cause a 404 error?

Consider this route:

Route::get('/profile/{user?}/{section?}', function ($user = 'guest', $section = 'overview') {
    return "$user - $section";
});

Visiting /profile returns a 404 error. Why?

Laravel

Route::get('/profile/{user?}/{section?}', function ($user = 'guest', $section = 'overview') {
    return "$user - $section";
});

A Because Laravel requires the first optional parameter if the second is optional, so both must be present or none.

B Because the route parameters are not marked optional correctly with question marks.

C Because the default values in the function are ignored by Laravel routing.

D Because Laravel does not support multiple optional parameters in routes.

💡 Hint

Think about how Laravel matches optional parameters in sequence.

Laravel requires that optional parameters be provided in order. If you have multiple optional parameters, you cannot skip the first and provide the second. Visiting /profile provides no parameters, so Laravel expects at least the first optional parameter to be present if the second is optional. This causes a 404.

🧠 Conceptual

expert

How does Laravel prioritize route matching with optional parameters?

Given these two routes:

Route::get('/product/{id}', function ($id) { return "Product $id"; });
Route::get('/product/{id?}', function ($id = 'default') { return "Optional Product $id"; });

What happens when you visit /product and why?

A It matches the first route and returns 'Product' with an empty id.

B It matches the first route and throws an error because id is missing.

C It causes a routing conflict error because both routes match the same URL.

D It matches the second route and returns 'Optional Product default' because the first route requires an id.

💡 Hint

Think about how Laravel matches routes in order and optional parameters.

Laravel matches routes in the order they are defined. The first route requires an id, so /product without id does not match it. The second route has an optional id, so /product matches it and returns 'Optional Product default'.