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.

Practice

1. Why do views in Rails present data to users?

easy

A. To store data in the database

B. To turn raw data into readable web pages

C. To handle user login and authentication

D. To manage server configuration settings

Solution

1. Step 1: Understand the role of views in MVC

   Views are responsible for showing data to users in a readable format, usually as HTML pages.

2. Step 2: Differentiate views from other parts

   Controllers prepare data, models handle data storage, but views present data clearly to users.

3. Final Answer:

   To turn raw data into readable web pages -> Option B

4. Quick Check:

   Views present data = To turn raw data into readable web pages [OK]

Hint: Views display data as pages, not store or process it [OK]

Common Mistakes:

• Confusing views with controllers or models
• Thinking views handle data storage
• Assuming views manage server settings

2. Which of the following is the correct way to insert Ruby data into a Rails view using ERB syntax?

easy

A. <% @user.name %>

B. [[ @user.name ]]

C. {{ @user.name }}

D. <%= @user.name %>

Solution

1. Step 1: Identify ERB syntax for output

   In Rails views, <%= %> outputs Ruby code result into HTML.

2. Step 2: Compare options

   <% %> runs Ruby code but does not output it; {{ }} and [[ ]] are not Rails ERB syntax.

3. Final Answer:

   <%= @user.name %> -> Option D

4. Quick Check:

   ERB output tag = <%= @user.name %> [OK]

Hint: Use <%= %> to show Ruby data in views [OK]

Common Mistakes:

• Using <% %> which does not output data
• Confusing with other template syntaxes like {{ }}
• Forgetting to use equals sign for output

3. Given the controller sets @items = ['apple', 'banana', 'cherry'], what will this view code output?

<ul>
  <% @items.each do |item| %>
    <li><%= item.upcase %></li>
  <% end %>
</ul>

medium

A. APPLEBANANACHERRY

B. applebananacherry

C. ItemItemItem

D. Syntax error due to missing output tag

Solution

1. Step 1: Understand the loop and method

   The code loops over @items and outputs each item in uppercase inside <li> tags.

2. Step 2: Check output tags and method

   <%= item.upcase %> outputs the uppercase string; the loop is correct.

3. Final Answer:

   <ul><li>APPLE</li><li>BANANA</li><li>CHERRY</li></ul> -> Option A

4. Quick Check:

   Loop with upcase output =
   • APPLE
   • BANANA
   • CHERRY
   [OK]

Hint: Look for <%= %> to output transformed data inside loop [OK]

Common Mistakes:

• Confusing <% %> with <%= %> causing no output
• Ignoring the upcase method effect
• Assuming original lowercase output

4. Identify the error in this Rails view snippet:

<ul>
  <% @products.each do |product| %>
    <li><%= product.name %></li>
  <% end %>
</ul>

medium

A. No error, code is correct

B. Using <%= inside <% block without closing properly

C. Incorrect ERB output tag syntax

D. Missing closing tag for <li>

Solution

1. Step 1: Inspect ERB tags inside the loop

   The code uses proper ERB syntax: <% %> for the loop, <%= product.name %> for output, and HTML tags correctly placed.

2. Step 2: Verify no syntax issues

   All tags are properly opened and closed; no mixing of ERB and HTML incorrectly.

3. Final Answer:

   No error, code is correct -> Option A

4. Quick Check:

   Valid Rails ERB view code = No error, code is correct [OK]

Hint: Ensure ERB tags <%= %> wrap only Ruby code, not HTML [OK]

Common Mistakes:

• Placing HTML closing bracket inside ERB tag
• Confusing <% and <%= tags
• Assuming no syntax error when mixing tags

5. You want to display a list of users with their email only if the email is present. Which view code correctly presents this conditional data?

<ul>
  <% @users.each do |user| %>
    <li>
      <%= user.name %>
      <% if user.email.present? %>
        (<%= user.email %>)
      <% end %>
    </li>
  <% end %>
</ul>

hard

A. Syntax error due to missing output tags

B. Always shows email even if empty

C. Correctly shows name and email only if email exists

D. Does not loop through users properly

Solution

1. Step 1: Analyze the loop and conditional

   The code loops over @users and shows user.name always.

2. Step 2: Check conditional email display

   The if condition checks if email is present, then outputs it inside parentheses.

3. Step 3: Verify ERB syntax correctness

   Output tags <%= %> are used properly for name and email; control flow tags <% %> for condition.

4. Final Answer:

   Correctly shows name and email only if email exists -> Option C

5. Quick Check:

   Conditional display with correct ERB = Correctly shows name and email only if email exists [OK]

Hint: Use <% if %> for conditions, <%= %> to output data [OK]

Common Mistakes:

• Using <%= for if without closing properly
• Outputting email without checking presence
• Forgetting to close loop or condition tags