Why Nested routes in Ruby on Rails? - Purpose & Use Cases

The Big Idea

Discover how nested routes turn messy URLs into clear, meaningful paths that tell a story.

The Scenario

Imagine building a website where you have blog posts and each post has comments. You try to write separate URLs for posts and comments manually, like /posts/1 and /comments/5, without showing which comment belongs to which post.

The Problem

Manually managing URLs for related data gets confusing fast. You might link to a comment without knowing its post, causing broken links or wrong pages. It's hard to keep URLs organized and meaningful, and updating them everywhere is a headache.

The Solution

Nested routes let you group related URLs clearly, like /posts/1/comments/5. Rails automatically understands the relationship, so your URLs stay clean and meaningful. This makes your app easier to build, read, and maintain.

Before vs After

✗ Before

get '/posts/:post_id'
get '/comments/:id'

✓ After

resources :posts do
  resources :comments
end

What It Enables

Nested routes make your URLs reflect real-world relationships, improving navigation and code clarity effortlessly.

Real Life Example

On a shopping site, products have reviews. Nested routes let you access reviews like /products/42/reviews/7, showing exactly which product the review belongs to.

Key Takeaways

Manual URL management for related data is confusing and error-prone.

Nested routes group related resources clearly in URLs.

This leads to cleaner code and better user navigation.