Format validation in Ruby on Rails - Step-by-Step Execution

Concept Flow - Format validation

Start: Model with attribute

↓

Apply format validation

↓

Save or update record

↓

Check attribute format

↓

Save success

↓

Save fails

Rails checks the attribute format when saving a record; if it matches the pattern, save succeeds, otherwise it fails with an error.

Execution Sample

Ruby on Rails

class User < ApplicationRecord
  validates :email, format: { with: /\A[^@\s]+@[^@\s]+\z/, message: "invalid email" }
end

This code validates that the email attribute matches a simple email pattern before saving.

Execution Table

Step	Action	Attribute Value	Format Check Result	Save Outcome	Error Messages
1	Create User with email '[e-mail]'	[e-mail]	Matches pattern	Success	None
2	Create User with email 'invalid-email'	invalid-email	Does not match pattern	Fail	email invalid email
3	Update User email to '[e-mail]'	[e-mail]	Matches pattern	Success	None
4	Update User email to 'bad@@domain'	bad@@domain	Does not match pattern	Fail	email invalid email

💡 Execution stops after save attempt; save fails if format validation does not pass.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4
email	nil	[e-mail]	invalid-email	[e-mail]	bad@@domain
save_success	nil	true	false	true	false
errors	empty	empty	email invalid email	empty	email invalid email

Key Moments - 2 Insights

Why does the save fail when the email is 'invalid-email'?

Because the email does not match the required pattern, as shown in execution_table row 2 where format check fails and an error message is added.

What happens to the errors when the email is valid?

Errors remain empty, meaning no validation errors, so save succeeds as shown in rows 1 and 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the save outcome at step 4?

A Pending

B Success

C Fail

D Error not checked

💡 Hint

Check the 'Save Outcome' column in row 4 of the execution_table.

At which step does the email first fail the format validation?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Format Check Result' column for each step in the execution_table.

If the regex pattern was changed to allow emails without '@', how would step 2 change?

A Save would still fail

B Save would succeed

C Error message would change

D No change

💡 Hint

Consider how the 'Format Check Result' affects 'Save Outcome' in the execution_table.

Concept Snapshot

Rails format validation checks if an attribute matches a regex pattern.
Use validates :attribute, format: { with: /pattern/, message: "error" }.
If format matches, save succeeds; otherwise, save fails with error.
Errors are added to the model's errors collection.
This helps ensure data like emails have correct format before saving.

Full Transcript

In Rails, format validation ensures an attribute matches a specific pattern before saving a record. The model uses validates with a regex to check the attribute. When saving, Rails checks the attribute's value against the pattern. If it matches, the save succeeds; if not, the save fails and an error message is added. For example, an email attribute validated with a regex will only save if the email looks correct. This prevents bad data from being stored. The execution table shows creating and updating users with valid and invalid emails, tracking save success and errors. Understanding this flow helps beginners see how Rails enforces data format rules.