Action methods in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an action method in a Rails controller?

An action method is a public method inside a Rails controller that responds to a web request and renders a view or redirects the user.

beginner

How does Rails know which action method to call for a URL?

Rails uses routing rules defined in config/routes.rb to map URLs to specific controller action methods.

intermediate

What happens if an action method does not explicitly render or redirect?

Rails automatically renders a view template matching the action method name unless you specify otherwise.

intermediate

Can private methods in a Rails controller be used as action methods?

No, only public methods can be action methods. Private or protected methods cannot be called as actions from a web request.

advanced

Why should action methods be kept simple and focused?

Keeping action methods simple improves readability, maintainability, and helps separate concerns by moving complex logic to models or helpers.

Which of the following is true about Rails action methods?

A They are always private methods.

B They must return a string.

C They respond to web requests and render views or redirect.

D They are defined in the model.

Action methods are public controller methods that handle requests and render or redirect.

What file defines the URL to action method mapping in Rails?

A config/routes.rb

B app/controllers/application_controller.rb

C app/views/layouts/application.html.erb

D config/database.yml

Routes in config/routes.rb map URLs to controller action methods.

If an action method does not call render or redirect, what does Rails do?

A Raises an error.

B Renders a view matching the action name.

C Redirects to the home page.

D Does nothing.

Rails automatically renders the view template matching the action method name.

Which methods cannot be used as action methods in Rails?

A Private and protected methods

B Public methods

C Methods defined in helpers

D Methods in models

Only public methods in controllers can be action methods.

Why is it good practice to keep action methods simple?

A To make the code harder to read.

B To avoid using models.

C To increase the number of lines in the controller.

D To improve readability and maintainability.

Simple action methods make code easier to read and maintain.

Explain what an action method is in Rails and how it relates to routing and views.

Think about how a URL leads to a method that shows a page.

Describe why private methods cannot be action methods and how to organize controller code effectively.

Consider access control and code clarity.

Practice

1. What is the primary role of an action method in a Rails controller?

easy

A. To respond to user requests by processing data and rendering views or redirects

B. To define database schema and migrations

C. To style the HTML pages with CSS

D. To manage server configuration settings

Solution

1. Step 1: Understand the purpose of action methods

   Action methods in Rails controllers handle user requests by processing data and deciding what to show next.

2. Step 2: Differentiate from other roles

   Database schema, styling, and server settings are handled elsewhere, not in action methods.

3. Final Answer:

   To respond to user requests by processing data and rendering views or redirects -> Option A

4. Quick Check:

   Action methods handle requests = A [OK]

Hint: Action methods handle requests and responses in controllers [OK]

Common Mistakes:

• Confusing action methods with database migrations
• Thinking action methods style pages
• Assuming action methods configure servers

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

easy

A. function show() {}

B. def show; end

C. show() => {}

D. def show() {}

Solution

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

   Rails controller actions are Ruby methods defined with def method_name; end.

2. Step 2: Identify correct syntax

   def show; end uses correct Ruby syntax without parentheses, which is common in Rails.

3. Final Answer:

   def show; end -> Option B

4. Quick Check:

   Ruby method syntax = A [OK]

Hint: Rails actions use Ruby method syntax: def name; end [OK]

Common Mistakes:

• Using JavaScript function syntax
• Adding parentheses with braces in Ruby
• Mixing arrow functions with Ruby

3. Given this Rails controller action:

def index
  @users = User.all
end

What will @users contain after this action runs?

medium

A. A hash of user attributes

B. A single User record

C. An array of all User records from the database

D. An empty array

Solution

1. Step 1: Understand User.all in Rails

   User.all fetches all records from the users table as an ActiveRecord collection (like an array).

2. Step 2: Determine the content of @users

   It will contain all user records, not just one or empty or a hash.

3. Final Answer:

   An array of all User records from the database -> Option C

4. Quick Check:

   User.all returns all records = D [OK]

Hint: User.all fetches all records as a collection [OK]

Common Mistakes:

• Thinking User.all returns a single record
• Assuming it returns a hash
• Confusing with empty array if no users exist

4. Identify the error in this Rails controller action:

def create
  @user = User.new(params[:user])
  if @user.save
    redirect_to @user
  else
    render :new
  end
end

medium

A. Missing an end keyword

B. Using render instead of redirect_to in else

C. Redirecting to @user instead of a URL string

D. Using params[:user] directly without strong parameters

Solution

1. Step 1: Check parameter handling in create action

   Rails requires strong parameters to whitelist allowed attributes for security.

2. Step 2: Identify misuse of params[:user]

   Using params[:user] directly is unsafe and will cause an error in modern Rails.

3. Final Answer:

   Using params[:user] directly without strong parameters -> Option D

4. Quick Check:

   Strong parameters needed = B [OK]

Hint: Always use strong parameters for mass assignment [OK]

Common Mistakes:

• Ignoring strong parameters security
• Thinking redirect_to needs a URL string only
• Missing end keyword (not true here)

5. You want to add a custom action method publish to your PostsController that changes a post's status to 'published' and then redirects to the post's page. Which code snippet correctly implements this?

hard

A. def publish
@post = Post.find(params[:id])
@post.status = 'published'
@post.save
redirect_to post_path(@post)
end

B. def publish
@post = Post.find(params[:id])
@post.status = 'published'
redirect_to post_path(@post)
end

C. def publish
@post = Post.find(params[:id])
@post.status = 'published'
redirect_to @post
end

D. def publish
@post = Post.find(params[:id])
@post.save(status: 'published')
redirect_to @post
end

Solution

1. Step 1: Find the post by ID

   All options correctly find the post using Post.find(params[:id]).

2. Step 2: Update the post's status and save changes

   def publish @post = Post.find(params[:id]) @post.status = 'published' redirect_to @post end changes status but does not save. def publish @post = Post.find(params[:id]) @post.status = 'published' redirect_to post_path(@post) end changes status but does not save. def publish @post = Post.find(params[:id]) @post.status = 'published' @post.save redirect_to post_path(@post) end changes status, calls save, then redirects. def publish @post = Post.find(params[:id]) @post.save(status: 'published') redirect_to @post end incorrectly uses save(status: 'published') which is invalid.

3. Step 3: Redirect to the post's show page

   Options A, C, and D redirect correctly. def publish @post = Post.find(params[:id]) @post.status = 'published' redirect_to post_path(@post) end uses post_path(@post) which is also correct.

4. Final Answer:

   def publish @post = Post.find(params[:id]) @post.status = 'published' @post.save redirect_to post_path(@post) end -> Option A

5. Quick Check:

   Change attribute + save + redirect = C [OK]

Hint: Change attribute, save record, then redirect [OK]

Common Mistakes:

• Forgetting to save after changing attribute
• Using invalid save syntax with parameters
• Not redirecting after update