Why controllers handle requests in Ruby on Rails - See It in Action

Understanding Why Controllers Handle Requests in Rails

📖 Scenario: You are building a simple web application using Ruby on Rails. The app needs to respond to user actions like visiting a page or submitting a form.In Rails, controllers are the parts that receive these user requests and decide what to do next.

🎯 Goal: Learn how to create a controller in Rails that handles a web request by defining an action method.This will show how controllers act as the middleman between the user and the app's response.

📋 What You'll Learn

Create a controller named WelcomeController

Add an action method called home inside the controller

Set up a route that directs the root URL / to WelcomeController#home

Create a simple view template that displays a welcome message

💡 Why This Matters

🌍 Real World

Web applications need to respond to user actions like clicking links or submitting forms. Controllers handle these requests and decide what the user sees next.

💼 Career

Understanding controllers is essential for building web apps with Rails, a popular framework used by many companies.

1

Create the WelcomeController

Create a controller class named WelcomeController that inherits from ApplicationController.

Ruby on Rails

# Your code here

Hint

Controllers in Rails are classes that inherit from ApplicationController.

2

Add the home action method

Inside the WelcomeController, add a method named home with no parameters.

Ruby on Rails

class WelcomeController < ApplicationController
  # Define the home action method here
  # Your code here
end

Hint

Action methods in controllers are simple methods that respond to requests.

3

Set the root route to WelcomeController#home

In the config/routes.rb file, add a line to set the root URL / to the home action of WelcomeController.

Ruby on Rails

class WelcomeController < ApplicationController
  def home
  end
end

# Add root route below
# Your code here

Hint

The root route directs the base URL to a controller action using the syntax root 'controller#action'.

4

Create a view template for the home action

Create a file named home.html.erb inside app/views/welcome/ folder. Inside it, add a heading with the text Welcome to Rails!.

Ruby on Rails

class WelcomeController < ApplicationController
  def home
  end
end

Rails.application.routes.draw do
  root 'welcome#home'
end

# Create app/views/welcome/home.html.erb with a heading
# Your code here

Hint

Views are HTML files with embedded Ruby placed in app/views/controller_name/.

Practice

1. Why do Rails controllers handle user requests?

easy

A. To decide how the app should respond to user actions

B. To store data permanently in the database

C. To style the web pages with CSS

D. To manage server hardware resources

Solution

1. Step 1: Understand the role of controllers in Rails

   Controllers receive user requests and decide what the app should do next, such as showing a page or saving data.

2. Step 2: Differentiate controller responsibilities from other parts

   Storing data is handled by models, styling by CSS, and hardware management is outside Rails scope.

3. Final Answer:

   To decide how the app should respond to user actions -> Option A

4. Quick Check:

   Controllers handle requests = A [OK]

Hint: Controllers decide app response to user actions [OK]

Common Mistakes:

• Confusing controllers with models for data storage
• Thinking controllers handle styling or hardware
• Believing controllers directly manage databases

2. Which of the following is the correct way to define an action named show in a Rails controller?

easy

A. function show() {
// action code
}

B. def show
# action code
end

C. show => {
// action code
}

D. action show {
// action code
}

Solution

1. Step 1: Recall Ruby method syntax in Rails controllers

   Rails controller actions are Ruby methods defined with def action_name and end.

2. Step 2: Identify correct syntax among options

   def show # action code end uses Ruby method syntax; others use JavaScript or invalid syntax.

3. Final Answer:

   def show\n # action code\nend -> Option B

4. Quick Check:

   Ruby method syntax = A [OK]

Hint: Rails actions are Ruby methods using def/end [OK]

Common Mistakes:

• Using JavaScript function syntax in Rails controllers
• Trying to define actions with arrow functions
• Using invalid keywords like 'action'

3. Given this controller code, what will be the rendered output when visiting /welcome/greet?

class WelcomeController < ApplicationController
  def greet
    @message = "Hello, Rails!"
  end
end

Assuming the view greet.html.erb contains:

<h1><%= @message %></h1>

medium

A. Hello, Rails!

B. <%= @message %>

C. Hello, Rails!

D. Error: undefined variable

Solution

1. Step 1: Understand controller sets instance variable

   The controller action greet sets @message to "Hello, Rails!" which is accessible in the view.

2. Step 2: View renders the instance variable inside <h1> tags

   The view uses ERB syntax <%= @message %> to insert the message text inside an <h1> element.

3. Final Answer:

   <h1>Hello, Rails!</h1> -> Option C

4. Quick Check:

   Instance variable rendered in view = B [OK]

Hint: Instance variables in controller appear in views with <%= %> [OK]

Common Mistakes:

• Expecting raw variable name instead of its value
• Confusing plain text with HTML tags
• Assuming variable is undefined without @

4. Identify the error in this controller code snippet:

class ProductsController < ApplicationController
  def index
    @products = Product.all
  end

  def show
    @product = Product.find(params[:id])
  end

  def create
    product = Product.new(params[:product])
    if product.save
      redirect_to product_path(product)
    else
      render :new
    end
  end
end

medium

A. Using params[:product] directly without strong parameters

B. Missing return statement in create action

C. No instance variable @product in create action

D. Incorrect inheritance from ApplicationController

Solution

1. Step 1: Review how parameters are handled in create action

   The code uses params[:product] directly, which is unsafe and disallowed in modern Rails without strong parameters.

2. Step 2: Identify missing strong parameters usage

   Rails requires filtering params with methods like product_params to permit only allowed attributes.

3. Final Answer:

   Using params[:product] directly without strong parameters -> Option A

4. Quick Check:

   Strong parameters required = D [OK]

Hint: Always use strong parameters to permit attributes [OK]

Common Mistakes:

• Ignoring strong parameters and using raw params
• Thinking return statements are needed in Rails actions
• Confusing instance variables with local variables

5. You want a controller action to handle both showing a form and processing form data for creating a new user. Which approach best follows Rails controller patterns?

hard

A. Use one action create to show form and save user

B. Use one action new to both show form and save user

C. Handle form display and data processing in the view file

D. Use separate actions: new to show form, create to process data

Solution

1. Step 1: Understand Rails RESTful controller conventions

   Rails uses separate actions: new to display the form, and create to handle form submission and save data.

2. Step 2: Evaluate options against best practices

   Combining form display and data processing in one action or view breaks separation of concerns and Rails conventions.

3. Final Answer:

   Use separate actions: new to show form, create to process data -> Option D

4. Quick Check:

   Separate new and create actions = C [OK]

Hint: Use new for form, create for saving data [OK]

Common Mistakes:

• Combining form display and processing in one action
• Trying to handle logic inside views
• Ignoring Rails RESTful conventions