App folder organization in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the app/models folder in a Rails application?

The app/models folder holds the Ruby classes that represent the data and business logic of the application. Models interact with the database and define rules for data.

beginner

What kind of files do you find in the app/controllers folder?

The app/controllers folder contains controller classes. Controllers receive user requests, interact with models, and decide which views to show.

beginner

Explain the role of the app/views folder in Rails.

The app/views folder stores template files that generate the HTML shown to users. Views display data provided by controllers in a user-friendly way.

intermediate

What is stored in the app/helpers folder and why is it useful?

The app/helpers folder contains helper modules. Helpers provide reusable methods to keep view templates clean and DRY (Don't Repeat Yourself).

beginner

Why is the app/assets folder important in a Rails app?

The app/assets folder holds static files like CSS, JavaScript, and images. These files control the look and feel and interactive behavior of the app.

Which folder in a Rails app contains the database interaction logic?

A app/helpers

B app/views

C app/models

D app/controllers

Models handle data and database logic in Rails, so they live in app/models.

Where do you put code that decides what HTML to show to users?

A app/views

B app/models

C app/controllers

D app/assets

Views contain templates that generate HTML for users.

If you want to add a method to help format dates in your views, where should you add it?

A app/models

B app/helpers

C app/controllers

D app/assets

Helpers provide reusable methods for views, so date formatting helpers go in app/helpers.

Which folder contains JavaScript and CSS files in a Rails app?

A app/models

B app/controllers

C app/views

D app/assets

Static files like JavaScript and CSS are stored in app/assets.

Controllers in Rails are responsible for:

A Handling user requests and directing flow

B Rendering HTML templates

C Interacting with the database

D Storing static files

Controllers handle user requests and decide what to do next.

Describe the main folders inside the app directory of a Rails application and their roles.

Think about the MVC pattern and where each part fits.

Explain how the organization of the app folder helps keep a Rails application clean and easy to maintain.

Consider how dividing tasks into folders helps teamwork and code clarity.

Practice

1. What is the main purpose of the app/ folder in a Rails application?

easy

A. To store database backups and logs

B. To hold static assets like images and stylesheets

C. To keep configuration files for the server

D. To organize the code by its role, like models, views, and controllers

Solution

1. Step 1: Understand the role of app/ folder

   The app/ folder is designed to organize the main parts of the Rails app code by their function.

2. Step 2: Identify what belongs in app/

   Models, views, and controllers are the core components stored in app/, not backups or static files.

3. Final Answer:

   To organize the code by its role, like models, views, and controllers -> Option D

4. Quick Check:

   App folder organizes code by role = B [OK]

Hint: Remember MVC parts live inside app/ folder [OK]

Common Mistakes:

• Confusing app/ with config/ or public/ folders
• Thinking assets like images go inside app/
• Assuming app/ holds database files

2. Which folder inside app/ should contain the code that responds to user requests?

easy

A. controllers

B. views

C. models

D. helpers

Solution

1. Step 1: Identify the role of controllers

   Controllers handle incoming user requests and decide what to do next.

2. Step 2: Match folder to role

   The controllers folder contains this code, while models manage data and views display content.

3. Final Answer:

   controllers -> Option A

4. Quick Check:

   Request handling = controllers = C [OK]

Hint: Controllers respond to requests inside app/ [OK]

Common Mistakes:

• Choosing models instead of controllers
• Confusing views with controllers
• Thinking helpers handle requests

3. Given this folder structure inside app/:
app/models/user.rb,
app/controllers/users_controller.rb,
app/views/users/index.html.erb
What is the role of users_controller.rb?

medium

A. It contains the HTML layout for user pages

B. It defines how user data is stored in the database

C. It manages the logic to handle user-related requests

D. It stores user session information

Solution

1. Step 1: Identify the controller file

   The file users_controller.rb is inside the controllers folder, so it handles requests.

2. Step 2: Understand controller responsibility

   Controllers manage logic for requests, not data storage or views.

3. Final Answer:

   It manages the logic to handle user-related requests -> Option C

4. Quick Check:

   Controller file handles requests = A [OK]

Hint: Controllers handle logic for requests, not data or views [OK]

Common Mistakes:

• Confusing controller with model responsibilities
• Thinking controller holds HTML templates
• Assuming controller stores session data

4. You accidentally put a view template file inside app/models/. What problem will this cause?

medium

A. The view will not render because Rails looks for templates only in app/views/

B. No problem; Rails loads views from any folder inside app/

C. The model will try to execute the view code causing a crash

D. Rails will raise an error because views must be in app/views/

Solution

1. Step 1: Understand Rails folder conventions

   Rails expects view templates only inside app/views/ to render them properly.

2. Step 2: Identify effect of wrong folder

   If a view is inside app/models/, Rails will not find it and won't render it.

3. Final Answer:

   The view will not render because Rails looks for templates only in app/views/ -> Option A

4. Quick Check:

   Views must be in app/views = D [OK]

Hint: Views only render from app/views folder [OK]

Common Mistakes:

• Expecting Rails to raise an error immediately
• Thinking models execute view code
• Assuming views load from anywhere in app/

5. You want to add a new feature that sends emails when a user signs up. Where should you place the mailer class in the Rails app/ folder structure?

hard

A. Inside app/controllers/ because it handles user actions

B. Inside app/mailers/ because mailers have their own folder

C. Inside app/models/ because it deals with user data

D. Inside app/views/ because emails have templates

Solution

1. Step 1: Recall Rails folder for mailers

   Rails has a dedicated app/mailers/ folder for mailer classes that send emails.

2. Step 2: Understand why mailers don't go elsewhere

   Controllers handle requests, models manage data, and views hold templates, but mailers have their own place.

3. Final Answer:

   Inside app/mailers/ because mailers have their own folder -> Option B

4. Quick Check:

   Mailers live in app/mailers = A [OK]

Hint: Put mailers in app/mailers folder [OK]

Common Mistakes:

• Placing mailers in controllers or models folders
• Confusing mailer classes with views
• Not knowing mailers have a separate folder