Why Before and after filters in Ruby on Rails? - Purpose & Use Cases

The Big Idea

What if you could write login checks and logs just once and have Rails do the rest automatically?

The Scenario

Imagine you have a web app where you must check user login before every page loads and log every action after it finishes.

You write this check and log code inside every controller action manually.

The Problem

Manually adding the same code everywhere is tiring and easy to forget.

If you miss one place, your app might let unauthorized users in or skip important logs.

It also makes your code messy and hard to update later.

The Solution

Before and after filters let you run code automatically before or after controller actions.

You write the check or log once, and Rails runs it for all relevant actions.

This keeps your code clean, consistent, and easy to maintain.

Before vs After

✗ Before

def show
  check_login
  # show action code
  log_action
end

✓ After

before_action :check_login
after_action :log_action

def show
  # show action code
end

What It Enables

You can easily add shared behavior across many actions without repeating code, making your app safer and cleaner.

Real Life Example

In a blog app, you want to verify the user is logged in before editing posts and log every edit after it happens.

Using filters, you add these checks once and they run automatically for all edit actions.

Key Takeaways

Manual repetition of checks and logs is error-prone and messy.

Before and after filters run code automatically around actions.

This keeps your app secure, clean, and easier to maintain.