Association callbacks in Ruby on Rails - Step-by-Step Execution

Concept Flow - Association callbacks

Trigger action on parent model

↓

Check association callback type

↓

before_add

↓

Run callback method if defined

↓

Modify associated objects or state

↓

Continue action

When you add or remove associated objects in Rails, specific callbacks run before or after the change to let you customize behavior.

Execution Sample

Ruby on Rails

class Cart < ApplicationRecord
  has_many :items, before_add: :check_stock

  def check_stock(item)
    raise 'Out of stock' if item.stock <= 0
  end
end

This code runs a method before adding an item to a cart to check if the item is in stock.

Execution Table

Step	Action	Callback Triggered	Callback Method Called	Effect	Result
1	Add item with stock=5 to cart.items	before_add	check_stock(item)	Checks item stock	Passes, item added
2	Add item with stock=0 to cart.items	before_add	check_stock(item)	Checks item stock	Raises 'Out of stock' error, item not added
3	Remove item from cart.items	before_remove	none (not defined)	No callback	Item removed normally
4	Add item to cart.items	after_add	none (not defined)	No callback	Item added normally
5	Remove item from cart.items	after_remove	none (not defined)	No callback	Item removed normally

💡 Execution stops after each add/remove action completes or raises error.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
cart.items.count	0	1	0	0	1	0
item.stock	varies	5	0	5	5	5

Key Moments - 2 Insights

Why does adding an item with zero stock raise an error?

Because the before_add callback runs check_stock, which raises an error if stock is 0, stopping the add (see execution_table step 2).

What happens if no callback method is defined for after_add or before_remove?

No callback runs, so the add or remove proceeds normally without extra checks (see execution_table steps 3,4,5).

Visual Quiz - 3 Questions

Look at the execution table, what is the cart.items.count after step 1?

A 1

B 0

C 2

D Undefined

💡 Hint

Check the variable_tracker row for cart.items.count after Step 1.

At which step does the before_add callback prevent adding an item?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table where an error is raised during before_add.

If we define an after_remove callback, what would happen at step 5?

A Callback method runs before item removal

B Callback method runs after item removal

C No callback runs

D Item removal is blocked

💡 Hint

After_remove callbacks run after removal actions, see concept_flow.

Concept Snapshot

Association callbacks in Rails run methods before or after adding/removing associated objects.
Use options like before_add, after_add, before_remove, after_remove in associations.
Callbacks let you check or modify objects during association changes.
If a before_* callback raises an error, the change is stopped.
Define callback methods in the model to customize behavior.

Full Transcript

In Rails, association callbacks let you run code when you add or remove objects from associations like has_many. For example, before_add runs before adding an object, and after_remove runs after removing one. You define methods in your model and link them with options like before_add: :method_name. When you add an item to a cart, the before_add callback can check if the item is in stock and stop the add if not. The execution table shows adding an item with stock 5 passes, but with stock 0 raises an error. Removing items without callbacks just works normally. This helps keep your data consistent and lets you run custom logic during association changes.