Controller methods and actions in Laravel - Step-by-Step Execution

Concept Flow - Controller methods and actions

HTTP Request Received

↓

Route Matches URL

↓

Controller Method Called

↓

Method Executes Action

↓

Return Response (View/Redirect/JSON)

↓

Response Sent to Browser

When a user visits a URL, Laravel finds the matching route, calls the controller method, which runs code and returns a response.

Execution Sample

Laravel

public function show($id) {
    $user = User::find($id);
    return view('user.profile', ['user' => $user]);
}

This method gets a user by ID and returns a profile view with user data.

Execution Table

Step	Action	Input/State	Output/Result
1	HTTP request to /user/5	URL: /user/5	Route matches 'user/{id}'
2	Call Controller@show	Parameter id=5	Method show(5) called
3	Find user by ID	User::find(5)	User object with id=5 or null
4	Return view	view('user.profile', ['user' => $user])	HTML page with user data
5	Send response	HTML content	Browser displays user profile

💡 Response sent to browser, request cycle ends

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
id	undefined	5	5	5
user	undefined	User object or null	User object or null	User object or null

Key Moments - 3 Insights

Why does the controller method receive the $id parameter?

Because the route defines a placeholder {id}, Laravel extracts it from the URL and passes it to the controller method as $id (see execution_table step 2).

What happens if User::find($id) returns null?

The method still returns the view, but the user variable will be null. The view should handle this case to avoid errors (see execution_table step 3).

How does the controller return a response to the browser?

By returning a view or other response object, Laravel converts it to HTML and sends it back to the browser (see execution_table steps 4 and 5).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of $id when the controller method is called?

A null

B undefined

C 5

D user object

💡 Hint

Check execution_table step 2 where the method is called with id=5

At which step does Laravel find the user object from the database?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table step 3 where User::find is called

If the route URL was /user/10, how would the variable tracker change?

A $id would be 10 instead of 5

B $user would be null always

C $id would be undefined

D No change in variables

💡 Hint

Variable $id tracks the route parameter, see variable_tracker for $id values

Concept Snapshot

Controller methods handle requests matched by routes.
Parameters from URLs are passed as method arguments.
Methods perform actions like fetching data.
Return views or responses to send HTML or JSON.
Laravel manages request to response flow automatically.

Full Transcript

When a user visits a URL, Laravel matches it to a route. The route calls a controller method, passing URL parts as parameters. The method runs code, like fetching a user by ID. It then returns a view with data. Laravel sends this view as HTML back to the browser. Variables like $id and $user change as the method runs. If the user is not found, the method still returns the view but with null data. This flow ensures user requests get proper responses.