Conditional validations in Ruby on Rails - Step-by-Step Execution

Concept Flow - Conditional validations

Start: Model instance created

↓

Check validation condition?

No→Skip validation

Yes↓

Run validation rule

↓

Validation passes?

No→Add error message

Yes↓

End

Rails checks if a condition is true before running a validation. If true, it validates; if false, it skips.

Execution Sample

Ruby on Rails

class User < ApplicationRecord
  validates :email, presence: true, if: :email_required?

  def email_required?
    admin?
  end
end

This code validates email presence only if the user is an admin.

Execution Table

Step	User.admin?	Condition (if: email_required?)	Validation run?	Validation result	Errors added
1	true	true	Yes	Pass	No
2	false	false	No	Skipped	No

💡 Validation stops after checking condition; if false, validation is skipped.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
admin?	nil	true	false	false
email_required?	nil	true	false	false
errors[:email]	[]	[]	[]	[]

Key Moments - 2 Insights

Why does the validation sometimes not run even if the attribute is empty?

Because the condition method (email_required?) returned false, so Rails skipped the validation as shown in execution_table row 2.

What happens if the condition method returns true but the attribute is valid?

Validation runs and passes, so no errors are added, as shown in execution_table row 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the validation result when admin? is false?

A Validation passes

B Validation is skipped

C Validation fails

D Error is added

💡 Hint

Check row 2 under 'Validation result' in the execution_table.

At which step does Rails add an error message?

A Neither step

B Step 2

C Step 1

D Both steps

💡 Hint

Look at the 'Errors added' column in the execution_table for both steps.

If admin? always returns true, how does the validation behave?

A Validation runs only if email is present

B Validation never runs

C Validation always runs

D Validation runs only if email is absent

💡 Hint

Refer to the 'Condition' and 'Validation run?' columns in the execution_table.

Concept Snapshot

Rails conditional validations run only if a condition is true.
Use :if or :unless with a method or proc.
If condition false, validation skips.
Errors added only if validation runs and fails.
Example: validates :email, presence: true, if: :admin?
This keeps validations flexible and efficient.

Full Transcript

In Rails, conditional validations let you run validations only when certain conditions are met. For example, you can validate an email only if the user is an admin. The flow starts when a model instance is created. Rails checks the condition method, like admin?. If it returns true, Rails runs the validation. If the validation passes, no errors are added. If it fails, errors are added to the model. If the condition returns false, Rails skips the validation entirely. This helps avoid unnecessary checks and keeps your model logic clean. The example code shows a User model validating email presence only if admin? returns true. The execution table shows two cases: when admin? is true, validation runs and passes; when false, validation is skipped. Variables like admin? and email_required? change accordingly during execution. Common confusions include why validations sometimes don't run (because condition is false) and when errors get added (only if validation runs and fails). The quiz questions help reinforce understanding by asking about validation results and error additions based on the execution table. Overall, conditional validations make your Rails models smarter and more efficient by running checks only when needed.