Route definition in routes.rb in Ruby on Rails - Step-by-Step Execution

Concept Flow - Route definition in routes.rb

Start routes.rb file

↓

Define route method (get/post/etc)

↓

Specify URL path

↓

Map to controller#action

↓

Rails adds route to routing table

↓

Request matches route -> controller action called

↓

Response sent back to browser

This flow shows how Rails reads route definitions, adds them to its routing table, and uses them to direct web requests to the right controller actions.

Execution Sample

Ruby on Rails

get '/welcome', to: 'home#welcome'
post '/login', to: 'sessions#create'
root 'home#index'

Defines three routes: a GET route to welcome page, a POST route for login, and the root URL mapped to home#index.

Execution Table

Step	Route Method	URL Path	Controller#Action	Routing Table State
1	get	/welcome	home#welcome	Added GET /welcome -> home#welcome
2	post	/login	sessions#create	Added POST /login -> sessions#create
3	root	/	home#index	Added root / -> home#index
4	Request: GET /welcome	N/A	home#welcome	Matches GET /welcome route, calls home#welcome
5	Request: POST /login	N/A	sessions#create	Matches POST /login route, calls sessions#create
6	Request: GET /	N/A	home#index	Matches root route, calls home#index
7	Request: GET /unknown	N/A	No route	No matching route found, returns 404

💡 Routing stops when a matching route is found or returns 404 if none matches.

Variable Tracker

Routing Table	Start	After Step 1	After Step 2	After Step 3	Final
Routes	empty	GET /welcome -> home#welcome	GET /welcome -> home#welcome, POST /login -> sessions#create	GET /welcome -> home#welcome, POST /login -> sessions#create, root / -> home#index	GET /welcome, POST /login, root / routes defined

Key Moments - 3 Insights

Why does the root route use 'root' instead of get/post?

The root route is a special shortcut in Rails to define the home page URL ('/'). It always responds to GET requests. See execution_table row 3 where 'root' adds '/' route.

What happens if a request URL does not match any route?

Rails returns a 404 error because no route matches. This is shown in execution_table row 7 where GET /unknown has no matching route.

Can the same URL path have different routes for GET and POST?

Yes, GET and POST are different HTTP methods. Routes can differ by method even if URL path is same, as in rows 1 and 2.

Visual Quiz - 3 Questions

Look at the execution_table, what controller action is called for a GET request to '/welcome'?

A home#welcome

B sessions#create

C home#index

D No route

💡 Hint

Check execution_table row 4 for GET /welcome request.

At which step does the root route get added to the routing table?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at execution_table rows 1-3 for route additions.

If you send a POST request to '/welcome', what happens according to the execution_table?

A Calls home#welcome

B Returns 404 No route

C Calls sessions#create

D Calls home#index

💡 Hint

Check if POST /welcome route is defined in execution_table rows 1-3 and request matches in rows 4-7.

Concept Snapshot

Rails routes.rb defines URL paths and HTTP methods
Routes map to controller#action pairs
Use get/post/put/delete or root for home page
Rails builds routing table from these definitions
Requests match routes by method and path
No match returns 404 error

Full Transcript

In Rails, the routes.rb file defines how URLs connect to controller actions. Each route specifies an HTTP method like get or post, a URL path, and the controller and action to run. Rails reads these routes and builds a routing table. When a web request comes in, Rails looks up the routing table to find the matching route by method and path. If found, it calls the controller action. If no route matches, Rails returns a 404 error. The root route is a special shortcut for the home page URL '/'. This visual trace shows adding routes and how requests match them step-by-step.

Practice

1. What is the purpose of defining routes in the routes.rb file in a Rails application?

easy

A. To manage user sessions

B. To write database queries

C. To style the web pages

D. To connect URLs to specific controller actions

Solution

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

   Routes define how incoming web requests are matched to controller actions.

2. Step 2: Identify the correct purpose

   Connecting URLs to controller actions allows the app to respond correctly to user requests.

3. Final Answer:

   To connect URLs to specific controller actions -> Option D

4. Quick Check:

   Routes link URLs to actions [OK]

Hint: Routes map URLs to controller actions [OK]

Common Mistakes:

• Confusing routes with database queries
• Thinking routes handle styling
• Assuming routes manage sessions

2. Which of the following is the correct syntax to define a GET route for the URL /home that maps to the index action of the pages controller?

easy

A. route get '/home' => 'pages#index'

B. get 'pages#index', to: '/home'

C. get '/home', to: 'pages#index'

D. post '/home', to: 'pages#index'

Solution

1. Step 1: Recall the syntax for GET routes in Rails

   The correct syntax is get 'url', to: 'controller#action'.

2. Step 2: Match the URL and controller#action correctly

   get '/home', to: 'pages#index' correctly uses get '/home', to: 'pages#index'.

3. Final Answer:

   get '/home', to: 'pages#index' -> Option C

4. Quick Check:

   GET route syntax = get 'url', to: 'controller#action' [OK]

Hint: Use get 'url', to: 'controller#action' for GET routes [OK]

Common Mistakes:

• Swapping URL and controller#action positions
• Using post instead of get for GET routes
• Incorrect syntax like 'route get'

3. Given the following route definition in routes.rb:

resources :articles, only: [:index, :show]

What URLs will be available and which controller actions will they map to?

medium

A. /articles (GET) -> articles#index and /articles/:id (GET) -> articles#show

B. /articles/new (GET) -> articles#new and /articles/:id/edit (GET) -> articles#edit

C. /articles (POST) -> articles#create and /articles/:id (PATCH) -> articles#update

D. /articles/:id (DELETE) -> articles#destroy and /articles (GET) -> articles#index

Solution

1. Step 1: Understand the resources with only option

   It limits routes to only index and show actions.

2. Step 2: Identify URLs and actions for index and show

   index maps to GET /articles, show maps to GET /articles/:id.

3. Final Answer:

   /articles (GET) -> articles#index and /articles/:id (GET) -> articles#show -> Option A

4. Quick Check:

   resources with only index, show = GET /articles and GET /articles/:id [OK]

Hint: Only index and show create GET /collection and GET /collection/:id [OK]

Common Mistakes:

• Assuming all RESTful routes are created
• Confusing HTTP verbs for actions
• Mixing up new/edit with index/show

4. Identify the error in this route definition:

get '/profile', controller: 'users', action: 'show'

medium

A. URL should not start with a slash

B. Missing 'to:' keyword before controller#action

C. Should use 'post' instead of 'get'

D. Controller name should be capitalized

Solution

1. Step 1: Check correct syntax for get route with controller and action

   The correct syntax uses to: 'controller#action', not separate keys.

2. Step 2: Identify the missing 'to:' keyword

   The given code misses to: and incorrectly uses separate keys.

3. Final Answer:

   Missing 'to:' keyword before controller#action -> Option B

4. Quick Check:

   Use get '/url', to: 'controller#action' [OK]

Hint: Use 'to:' keyword for controller#action in routes [OK]

Common Mistakes:

• Omitting 'to:' keyword
• Using wrong HTTP verb
• Incorrect URL format

5. You want to create routes for a blog with posts and nested comments. Which route definition correctly creates RESTful routes for posts and nested comments inside routes.rb?

hard

A. resources :posts do
resources :comments
end

B. resources :posts, comments: true

C. resource :posts do
resource :comments
end

D. get '/posts/:post_id/comments', to: 'comments#index' only

Solution

1. Step 1: Understand nested resources syntax

   Nested resources are defined by placing one resources block inside another.

2. Step 2: Identify correct nested syntax for posts and comments

   resources :posts do resources :comments end correctly nests comments inside posts using a block.

3. Final Answer:

   resources :posts do resources :comments end -> Option A

4. Quick Check:

   Nested resources use block syntax [OK]

Hint: Nest resources inside block for nested routes [OK]

Common Mistakes:

• Using singular 'resource' instead of plural 'resources'
• Trying to pass nested resources as options
• Defining only one route manually