Route parameters in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a route parameter in Laravel?

A route parameter is a placeholder in a URL that captures dynamic values from the URL and passes them to the controller or closure handling the route.

beginner

How do you define a required route parameter in Laravel?

You define a required route parameter by placing curly braces around the parameter name in the route URI, like /user/{id}. This means the URL must include a value for id.

beginner

What happens if you visit a Laravel route with a missing required parameter?

Laravel will return a 404 Not Found error because the route expects a parameter value and it was not provided in the URL.

intermediate

How do you define an optional route parameter in Laravel?

You add a question mark after the parameter name inside the braces, like /user/{name?}. You should also provide a default value in the controller or closure to handle when the parameter is missing.

intermediate

How can you restrict a route parameter to only accept numbers in Laravel?

You use the where method on the route to add a regular expression constraint, for example: Route::get('/user/{id}', ...)->where('id', '[0-9]+'); This ensures only numeric values are accepted.

How do you define a required route parameter in Laravel?

A Use curly braces around the parameter name, e.g., /user/{id}

B Use square brackets around the parameter name, e.g., /user/[id]

C Use parentheses around the parameter name, e.g., /user/(id)

D Use angle brackets around the parameter name, e.g., /user/<id>

Required route parameters are defined with curly braces like /user/{id}.

What symbol makes a route parameter optional in Laravel?

A Exclamation mark (!)

B Dollar sign ($)

C Question mark (?)

D Asterisk (*)

Adding a question mark after the parameter name makes it optional, e.g., {name?}.

What happens if you visit a route missing a required parameter?

A Laravel shows a 404 Not Found error

B Laravel redirects to homepage

C Laravel shows a blank page

D Laravel automatically fills the parameter with null

Missing required parameters cause Laravel to return a 404 error.

How do you restrict a route parameter to only numbers?

A Use ->restrict('param', 'numbers') on the route

B Use ->onlyNumbers() on the route

C Use ->validate('param', 'numeric') on the route

D Use ->where('param', '[0-9]+') on the route

The where method with a regex like '[0-9]+' restricts the parameter to numbers.

Which of these is a valid route with an optional parameter?

A /post/{id}

B /post/{id?}

C /post/[id]

D /post/(id)

Optional parameters use a question mark inside curly braces: {id?}.

Explain how to create a Laravel route with a required parameter and how Laravel handles the parameter value.

Think about how URLs can carry dynamic info.

Describe how to make a route parameter optional and how to handle it in the controller.

Optional means it can be there or not.

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