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.

Practice

1. What is the main purpose of format validation in Rails models?

easy

A. To ensure data matches a specific pattern using regular expressions

B. To check if a field is present and not empty

C. To verify numerical values are within a range

D. To automatically format dates for display

Solution

1. Step 1: Understand format validation role

   Format validation uses regular expressions to check if data fits a pattern.

2. Step 2: Compare with other validations

   Presence validation checks if data exists, numericality checks numbers, and formatting dates is unrelated.

3. Final Answer:

   To ensure data matches a specific pattern using regular expressions -> Option A

4. Quick Check:

   Format validation = pattern check [OK]

Hint: Format validation = pattern matching with regex [OK]

Common Mistakes:

• Confusing format validation with presence validation
• Thinking format validation changes data format
• Mixing format validation with numerical range checks

2. Which of the following is the correct syntax to validate an email format in a Rails model?

easy

A. validates_format_of :email, with: /\A[^@\s]+@[^@\s]+\z/

B. validate :email, format: /\A[^@\s]+@[^@\s]+\z/

C. validates :email, format: { with: /\A[^@\s]+@[^@\s]+\z/ }

D. validates :email, regex: /\A[^@\s]+@[^@\s]+\z/

Solution

1. Step 1: Identify correct validation method

   Rails uses validates with format: { with: REGEX } syntax for format validation.

2. Step 2: Check syntax correctness

   validates :email, format: { with: /\A[^@\s]+@[^@\s]+\z/ } correctly uses validates :email, format: { with: /regex/ }. validate :email, format: /\A[^@\s]+@[^@\s]+\z/ uses wrong method validate. validates_format_of :email, with: /\A[^@\s]+@[^@\s]+\z/ uses deprecated validates_format_of. validates :email, regex: /\A[^@\s]+@[^@\s]+\z/ uses invalid key regex.

3. Final Answer:

   validates :email, format: { with: /\A[^@\s]+@[^@\s]+\z/ } -> Option C

4. Quick Check:

   Correct syntax = validates :email, format: { with: /\A[^@\s]+@[^@\s]+\z/ } [OK]

Hint: Use validates with format: { with: regex } [OK]

Common Mistakes:

• Using validate instead of validates
• Using invalid keys like regex instead of format
• Using deprecated validates_format_of method

3. Given this model validation:

validates :username, format: { with: /\A[a-z0-9_]+\z/, message: "only allows lowercase letters, numbers, and underscores" }

What happens if you try to save username = "User123"?

medium

A. The record saves successfully

B. The record fails to save with a format error

C. The record saves but the username is changed to lowercase

D. A syntax error occurs

Solution

1. Step 1: Analyze the regex pattern

   The regex /\A[a-z0-9_]+\z/ allows only lowercase letters, digits, and underscores from start to end.

2. Step 2: Check the input against the pattern

   Input "User123" contains uppercase 'U', which does not match the pattern.

3. Final Answer:

   The record fails to save with a format error -> Option B

4. Quick Check:

   Uppercase breaks regex = validation fails [OK]

Hint: Regex is case sensitive; uppercase breaks lowercase-only pattern [OK]

Common Mistakes:

• Assuming validation auto-changes case
• Thinking uppercase letters are allowed
• Confusing syntax error with validation failure

4. Identify the error in this validation code:

validates :phone, format: { with: /\d{10}/, message: "must be 10 digits" }

medium

A. The regex does not anchor start and end, allowing invalid matches

B. The regex should be enclosed in quotes

C. The message key is misspelled

D. The validates method is missing a colon before phone

Solution

1. Step 1: Review the regex pattern

   The regex /\d{10}/ matches any 10 digits anywhere in the string, not necessarily the whole string.

2. Step 2: Understand validation implications

   Without anchors \A and \z, strings with extra characters before or after 10 digits will pass incorrectly.

3. Final Answer:

   The regex does not anchor start and end, allowing invalid matches -> Option A

4. Quick Check:

   Regex anchors needed for exact match [OK]

Hint: Always anchor regex with \A and \z for full string match [OK]

Common Mistakes:

• Forgetting to anchor regex start/end
• Assuming regex in quotes is required
• Misspelling keys like message or validates

5. You want to validate a postal code that must be exactly 5 digits or 5 digits followed by a dash and 4 digits (like '12345' or '12345-6789'). Which validation is correct?

hard

A. validates :postal_code, format: { with: /\A\d{5}-\d{4}\z/, message: "invalid postal code" }

B. validates :postal_code, format: { with: /\d{5}(-\d{4})?/, message: "invalid postal code" }

C. validates :postal_code, format: { with: /\A\d{9}\z/, message: "invalid postal code" }

D. validates :postal_code, format: { with: /\A\d{5}(-\d{4})?\z/, message: "invalid postal code" }

Solution

1. Step 1: Understand the postal code formats

   Valid formats are 5 digits alone or 5 digits plus dash and 4 digits.

2. Step 2: Analyze regex options

   validates :postal_code, format: { with: /\A\d{5}(-\d{4})?\z/, message: "invalid postal code" } uses anchors \A and \z and allows 5 digits with optional dash and 4 digits. validates :postal_code, format: { with: /\d{5}(-\d{4})?/, message: "invalid postal code" } lacks anchors, allowing partial matches. validates :postal_code, format: { with: /\A\d{5}-\d{4}\z/, message: "invalid postal code" } requires dash and 4 digits always, disallowing 5-digit only. validates :postal_code, format: { with: /\A\d{9}\z/, message: "invalid postal code" } requires exactly 9 digits, no dash.

3. Final Answer:

   validates :postal_code, format: { with: /\A\d{5}(-\d{4})?\z/, message: "invalid postal code" } -> Option D

4. Quick Check:

   Anchored regex with optional group = validates :postal_code, format: { with: /\A\d{5}(-\d{4})?\z/, message: "invalid postal code" } [OK]

Hint: Use anchors and optional group for flexible exact match [OK]

Common Mistakes:

• Omitting anchors causing partial matches
• Forcing dash and extra digits when optional
• Using wrong digit counts or missing optional group