Route parameters in Laravel - Step-by-Step Execution

Concept Flow - Route parameters

User visits URL

↓

Laravel checks routes

↓

Match route pattern with parameters

↓

Extract parameter values

↓

Pass parameters to controller or closure

↓

Return response with parameter data

Laravel matches the URL to a route pattern with parameters, extracts those parameters, and passes them to the handler.

Execution Sample

Laravel

Route::get('/user/{id}', function ($id) {
    return "User ID: $id";
});

Defines a route that captures the 'id' from the URL and returns it in the response.

Execution Table

Step	URL Visited	Route Pattern	Parameter Extracted	Handler Called	Response
1	/user/5	/user/{id}	id = 5	Closure with id=5	"User ID: 5"
2	/user/abc	/user/{id}	id = abc	Closure with id='abc'	"User ID: abc"
3	/user/	/user/{id}	No match	No handler	404 Not Found

💡 Execution stops when URL does not match any route pattern with required parameters.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
id	undefined	5	abc	undefined

Key Moments - 2 Insights

Why does '/user/' not match the route '/user/{id}'?

Because the route requires a parameter 'id' after '/user/', and '/user/' has nothing there, so no match occurs (see execution_table row 3).

Can the route parameter 'id' accept any value?

Yes, by default it accepts any string segment in the URL (see execution_table rows 1 and 2 where '5' and 'abc' are accepted).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'id' at step 2?

A undefined

B 5

C abc

D null

💡 Hint

Check the 'Parameter Extracted' column in execution_table row 2.

At which step does the URL fail to match the route pattern?

A Step 1

B Step 3

C Step 2

D None

💡 Hint

Look at the 'Route Pattern' and 'Parameter Extracted' columns in execution_table.

If the route was defined as '/user/{id}/profile', which URL would match?

A /user/5/profile

B /user/5

C /user/profile

D /user/5/extra

💡 Hint

The URL must exactly match the pattern including '/profile' after the parameter.

Concept Snapshot

Route parameters let Laravel capture parts of the URL as variables.
Syntax: '/path/{parameter}' captures 'parameter' from URL.
Laravel passes these to the route handler.
If URL part is missing, route does not match.
Parameters accept any string by default.

Full Transcript

When a user visits a URL, Laravel checks all defined routes to find a match. If a route has parameters like '/user/{id}', Laravel extracts the 'id' part from the URL. This value is then passed to the route's function or controller. For example, visiting '/user/5' sets 'id' to '5'. If the URL does not include the parameter, like '/user/', Laravel does not find a match and returns a 404 error. Parameters accept any string segment by default, so '/user/abc' works too. This process allows dynamic URLs that respond based on user input.

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