Why views present data in Ruby on Rails - Visual Breakdown

Concept Flow - Why views present data

Controller gets data

↓

Controller sends data to View

↓

View receives data

↓

View formats and displays data

↓

User sees the data on the screen

The controller fetches data and sends it to the view, which then formats and shows it to the user.

Execution Sample

Ruby on Rails

def show
  @user = User.find(params[:id])
end

# In show.html.erb
<p><%= @user.name %></p>

This code gets a user from the database and the view shows the user's name.

Execution Table

Step	Action	Data State	View Output
1	Controller receives request with user id	params[:id] = 3	No output yet
2	Controller finds user by id	@user = User(id:3, name:'Alice')	No output yet
3	Controller passes @user to view	@user available in view	No output yet
4	View reads @user.name	Access 'Alice'	Prepares to display 'Alice'
5	View renders HTML with user name	Data unchanged	<p>Alice</p>
6	User sees rendered HTML	Data unchanged	Alice shown on page

💡 View finishes rendering and user sees the data on the screen

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
params[:id]	nil	3	3	3
@user	nil	User(id:3, name:'Alice')	User(id:3, name:'Alice')	User(id:3, name:'Alice')

Key Moments - 2 Insights

Why does the view need the controller to send data?

The view only shows data; it does not get data itself. The controller fetches data and sends it to the view, as shown in steps 2 and 3 of the execution table.

Can the view change the data it receives?

No, the view only formats and displays data. It does not modify the data, which stays the same from step 3 to the final step.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of @user after step 2?

A User(id:3, name:'Alice')

B nil

C params[:id]

D 3

💡 Hint

Check the 'Data State' column at step 2 in the execution table.

At which step does the view start rendering the user name?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Look for when the view reads @user.name in the execution table.

If the controller did not find a user, what would the view receive?

A @user with user data

B nil or empty @user

C params[:id]

D An error message

💡 Hint

Think about what happens if User.find fails before passing data to the view.

Concept Snapshot

In Rails, the controller gets data from the model.
It sends this data to the view.
The view only shows the data, it does not fetch or change it.
This separation keeps code organized and clear.
Example: controller sets @user, view shows @user.name.

Full Transcript

In Rails, when a user requests a page, the controller first gets the needed data, like a user record from the database. Then, the controller sends this data to the view. The view's job is to take this data and turn it into HTML that the user can see. The view does not get data by itself or change it; it only presents it. This keeps the app organized: controllers handle data, views handle display. For example, the controller finds a user by id and sets @user. The view then uses @user.name to show the user's name on the page.