Route parameters in Ruby on Rails - Step-by-Step Execution

Concept Flow - Route parameters

User sends HTTP request

↓

Rails router matches URL pattern

↓

Extract route parameters from URL

↓

Pass parameters to controller action

↓

Controller uses parameters to find data

↓

Render response with data

Rails takes the URL, finds matching route, extracts parameters from it, and sends them to the controller to use.

Execution Sample

Ruby on Rails

get '/books/:id', to: 'books#show'

# URL: /books/42
# params[:id] will be '42'

This route captures the :id part from the URL and makes it available in params for the controller.

Execution Table

Step	URL Requested	Route Pattern Matched	Extracted Params	Controller Action	Action Parameter Value
1	/books/42	/books/:id	{ id: '42' }	books#show	params[:id] = '42'
2	/books/7	/books/:id	{ id: '7' }	books#show	params[:id] = '7'
3	/books	No match	{}	No action	No params
4	/books/abc	/books/:id	{ id: 'abc' }	books#show	params[:id] = 'abc'

💡 Routing stops when no matching route pattern is found or after controller action is called.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
params[:id]	nil	'42'	'7'	nil	'abc'

Key Moments - 2 Insights

Why does params[:id] have different values for different URLs?

Because the router extracts the part of the URL that matches :id in the route pattern, as shown in execution_table rows 1, 2, and 4.

What happens if the URL does not match the route pattern?

No route is matched, so no params are extracted and no controller action is called, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution table, what is params[:id] when the URL is '/books/7'?

A nil

B '7'

C '42'

D 'abc'

💡 Hint

Check execution_table row 2 under 'Action Parameter Value'

At which step does the router fail to find a matching route?

A Step 3

B Step 1

C Step 4

D Step 2

💡 Hint

Look at execution_table row 3 under 'Route Pattern Matched'

If the route pattern changed to '/books/:book_id', what would params key be for the URL '/books/42'?

A params[:id]

B params[:42]

C params[:book_id]

D params[:book]

💡 Hint

Route parameter names come from the pattern segment after the colon, see concept_flow

Concept Snapshot

Rails route parameters capture parts of the URL defined by :name in routes.
These parameters become keys in the params hash.
Controllers access params[:name] to get values.
If URL doesn't match route, no params are set.
Example: get '/books/:id' makes params[:id] available.

Full Transcript

In Rails, when a user sends a request URL, the router looks for a matching route pattern. If the pattern includes parts like :id, Rails extracts that part from the URL and puts it in params with the key 'id'. The controller action then uses params[:id] to find or show data. If the URL does not match any route, no parameters are extracted and no controller action runs. For example, the route get '/books/:id' matches URLs like /books/42 and sets params[:id] to '42'. This process helps Rails know what data the user wants based on the URL.

Practice

1. What does a route parameter in Rails do?
get '/users/:id', to: 'users#show'

easy

A. Captures part of the URL as a variable to use in the controller

B. Defines a fixed URL path without variables

C. Specifies the HTTP method to use

D. Sets the controller action to redirect to another page

Solution

1. Step 1: Understand the colon in the route path

   The colon before id means this part of the URL is a variable, called a route parameter.

2. Step 2: Role of route parameters in Rails

   This variable is captured from the URL and passed to the controller action for use, like finding a user by ID.

3. Final Answer:

   Captures part of the URL as a variable to use in the controller -> Option A

4. Quick Check:

   Route parameter = URL variable [OK]

Hint: Colon before name means URL part is a variable [OK]

Common Mistakes:

• Thinking route parameters define fixed paths
• Confusing route parameters with HTTP methods
• Assuming route parameters redirect to other pages

2. Which of the following is the correct syntax to define a route with a parameter named post_id in Rails?

easy

A. get '/posts/post_id', to: 'posts#show'

B. get '/posts/{post_id}', to: 'posts#show'

C. get '/posts/<post_id>', to: 'posts#show'

D. get '/posts/:post_id', to: 'posts#show'

Solution

1. Step 1: Identify correct route parameter syntax

   In Rails, route parameters use a colon before the name, like :post_id.

2. Step 2: Compare options

   Only get '/posts/:post_id', to: 'posts#show' uses the colon syntax correctly. Others use incorrect braces or no colon.

3. Final Answer:

   get '/posts/:post_id', to: 'posts#show' -> Option D

4. Quick Check:

   Colon before parameter name = correct syntax [OK]

Hint: Use colon before parameter name in route path [OK]

Common Mistakes:

• Using curly braces or angle brackets instead of colon
• Omitting colon before parameter name
• Confusing parameter syntax with query strings

3. Given this route:
get '/products/:id', to: 'products#show'
And this controller code:

def show
  @product_id = params[:id]
end

What will @product_id be if the URL is /products/42?

medium

A. The string '42'

B. The integer 42

C. nil

D. An error because params[:id] is undefined

Solution

1. Step 1: Understand route parameter capture

   The :id in the route captures the URL part '42' as a string in params[:id].

2. Step 2: Assigning params value in controller

   The controller assigns @product_id = params[:id], so @product_id is the string '42'. Rails does not convert it automatically to integer.

3. Final Answer:

   The string '42' -> Option A

4. Quick Check:

   Route params are strings by default [OK]

Hint: Route params are strings unless converted [OK]

Common Mistakes:

• Assuming params[:id] is an integer automatically
• Expecting nil if parameter is present
• Thinking params[:id] causes an error if defined in route

4. Identify the error in this route definition:

get '/orders/:order_id/items/:item_id', to: 'orders#item'

Controller action:

def item
  @order = Order.find(params[:id])
  @item = Item.find(params[:item_id])
end

medium

A. Route path should not have two parameters

B. params[:id] is incorrect; should be params[:order_id]

C. Controller action name should be 'show' not 'item'

D. Item.find should use params[:id] instead of params[:item_id]

Solution

1. Step 1: Check route parameters names

   The route defines parameters :order_id and :item_id, so params keys are :order_id and :item_id.

2. Step 2: Check controller parameter usage

   The controller incorrectly uses params[:id] which does not exist. It should use params[:order_id] to find the order.

3. Final Answer:

   params[:id] is incorrect; should be params[:order_id] -> Option B

4. Quick Check:

   Parameter names must match route keys [OK]

Hint: Match params keys exactly to route parameter names [OK]

Common Mistakes:

• Using generic :id when route uses :order_id
• Thinking multiple parameters are not allowed
• Confusing controller action names with route parameters

5. You want to create a nested route to show a comment belonging to a post using route parameters. Which route definition correctly captures both post_id and id for the comment?

hard

A. get '/posts/:id/comments/:post_id', to: 'comments#show'

B. get '/posts/comments/:post_id/:id', to: 'comments#show'

C. get '/posts/:post_id/comments/:id', to: 'comments#show'

D. get '/comments/:id/posts/:post_id', to: 'comments#show'

Solution

1. Step 1: Understand nested resource URL structure

   Nested routes usually put the parent resource first, then the child. Here, post_id comes before id for comment.

2. Step 2: Check route parameter order and names

   get '/posts/:post_id/comments/:id', to: 'comments#show' correctly uses /posts/:post_id/comments/:id capturing post's ID and comment's ID in order.

3. Final Answer:

   get '/posts/:post_id/comments/:id', to: 'comments#show' -> Option C

4. Quick Check:

   Parent ID first, child ID second in nested routes [OK]

Hint: Parent resource param before child in nested routes [OK]

Common Mistakes:

• Swapping order of post_id and comment id
• Putting parameters in wrong positions
• Using incorrect parameter names