Controller generation in Ruby on Rails - Mini Project: Build & Apply

Controller generation

📖 Scenario: You are building a simple blog application using Ruby on Rails. You need to create a controller to manage blog posts.

🎯 Goal: Create a Rails controller named PostsController with an index action that will later display all blog posts.

📋 What You'll Learn

Create a controller named PostsController

Add an index action method inside the controller

Ensure the controller inherits from ApplicationController

Use Rails conventions for controller generation

💡 Why This Matters

🌍 Real World

Controllers in Rails handle web requests and decide what to show users. Creating controllers is a core part of building web apps.

💼 Career

Rails developers frequently generate and customize controllers to build features and manage app flow.

1

Create the PostsController file

Create a file named posts_controller.rb inside the app/controllers directory with a class named PostsController that inherits from ApplicationController.

Ruby on Rails

# Your code here

Hint

Remember, Rails controllers are classes that inherit from ApplicationController.

2

Add the index action

Inside the PostsController class, add an empty method named index to serve as the action for listing posts.

Ruby on Rails

class PostsController < ApplicationController
  # Add the index action method below
  # Your code here
end

Hint

Actions in Rails controllers are defined as methods inside the controller class.

3

Generate the controller using Rails command

Write the Rails command to generate a controller named Posts with an index action. This command will create the controller file and the view folder automatically.

Ruby on Rails

# Your code here

Hint

Use the rails generate controller command followed by the controller name and action names.

4

Add a route for the index action

In the config/routes.rb file, add a route that maps the root URL / to the index action of the PostsController using the syntax root 'posts#index'.

Ruby on Rails

# Add the root route below
# Your code here

Hint

The root route defines what page loads when visiting the base URL of your app.

Practice

1. What does the rails generate controller command do in a Rails application?

easy

A. Compiles the Rails application for production.

B. Generates a new database table for storing data.

C. Deletes an existing controller and its views.

D. Creates a new controller file with specified actions and related view files.

Solution

1. Step 1: Understand the purpose of the command

   The rails generate controller command is used to create a new controller in a Rails app.

2. Step 2: Identify what files are created

   This command creates a controller file and also generates view files for the actions specified.

3. Final Answer:

   Creates a new controller file with specified actions and related view files. -> Option D

4. Quick Check:

   Controller generation = creates controller and views [OK]

Hint: Controller generator creates controller and views together [OK]

Common Mistakes:

• Confusing controller generation with database migration
• Thinking it compiles or deletes files
• Assuming it only creates views without controller

2. Which of the following is the correct syntax to generate a controller named Products with actions index and show?

easy

A. rails generate controller Products index show

B. rails create controller Products index show

C. rails generate model Products index show

D. rails generate controller products index show

Solution

1. Step 1: Identify the correct command keyword

   The correct command to generate a controller is rails generate controller.

2. Step 2: Check the controller name and actions

   Controller names are capitalized (e.g., Products) and actions follow after the name.

3. Final Answer:

   rails generate controller Products index show -> Option A

4. Quick Check:

   Correct syntax = rails generate controller + ControllerName + actions [OK]

Hint: Use 'rails generate controller' with capitalized controller name [OK]

Common Mistakes:

• Using 'create' instead of 'generate'
• Using 'model' instead of 'controller'
• Using lowercase controller name

3. Given the command rails generate controller Articles new edit, which files will be created?

medium

A. Only the controller file articles_controller.rb without views.

B. Model file article.rb and migration for articles table.

C. Controller file articles_controller.rb and views new.html.erb and edit.html.erb.

D. Database schema file and routes for articles.

Solution

1. Step 1: Understand what the generate controller command creates

   It creates a controller file named after the pluralized controller name and view files for each action.

2. Step 2: Identify the files created for actions

   Actions new and edit generate corresponding view files new.html.erb and edit.html.erb.

3. Final Answer:

   Controller file articles_controller.rb and views new.html.erb and edit.html.erb. -> Option C

4. Quick Check:

   Controller + views for actions = Controller file articles_controller.rb and views new.html.erb and edit.html.erb. [OK]

Hint: Controller generator creates views for each action named [OK]

Common Mistakes:

• Confusing controller generation with model generation
• Expecting database files to be created
• Thinking views are not created automatically

4. You run rails generate controller users show but get an error. Which of the following is the most likely cause?

medium

A. Controller name should be capitalized as Users.

B. The action show is not allowed in controllers.

C. You must create a model before generating a controller.

D. The command should be rails create controller users show.

Solution

1. Step 1: Check the controller name capitalization

   Rails expects controller names to be capitalized (e.g., Users), lowercase causes errors.

2. Step 2: Verify command correctness

   The command rails generate controller Users show is correct; show is a valid action.

3. Final Answer:

   Controller name should be capitalized as Users. -> Option A

4. Quick Check:

   Capitalized controller name required [OK]

Hint: Always capitalize controller names in generate command [OK]

Common Mistakes:

• Using lowercase controller names
• Thinking actions are restricted
• Confusing generate with create command

5. You want to generate a controller named Admin::Dashboard with actions index and stats. Which command correctly creates the controller and places it in the admin folder?

hard

A. rails generate controller admin/dashboard index stats

B. rails generate controller Admin::Dashboard index stats

C. rails generate controller Admin_Dashboard index stats

D. rails generate controller admin_dashboard index stats

Solution

1. Step 1: Understand namespacing in Rails controllers

   Using :: in the controller name creates a folder structure for namespacing (e.g., Admin::Dashboard creates admin/dashboard_controller.rb).

2. Step 2: Identify the correct command syntax

   The correct syntax uses capitalized names with :: to separate namespace and controller name.

3. Final Answer:

   rails generate controller Admin::Dashboard index stats -> Option B

4. Quick Check:

   Namespace with :: and capitalized names [OK]

Hint: Use :: for namespaced controllers with capitalized parts [OK]

Common Mistakes:

• Using underscores instead of :: for namespaces
• Using lowercase names for namespaces
• Confusing folder path with command syntax