Format validation in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to validate that the email attribute has the correct format.

Ruby on Rails

validates :email, format: { with: [1] }

Drag options to blanks, or click blank then click option'

A/\A[^@\s]+@[^@\s]+\z/

B/[a-z]+/

C/\s+/

D/\d+/

Attempts:

3 left

💡 Hint

Common Mistakes

Using a regex that matches only letters or digits.

Not anchoring the regex to start and end of string.

The regex /\A[^@\s]+@[^@\s]+\z/ ensures the email has a basic valid format with one '@' and no spaces.

2fill in blank

medium

Complete the code to add a custom error message for invalid email format.

Ruby on Rails

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

Drag options to blanks, or click blank then click option'

A"is invalid"

B"must be unique"

C"is too short"

D"can't be blank"

Attempts:

3 left

💡 Hint

Common Mistakes

Using messages unrelated to format validation.

Forgetting to put the message in quotes.

The message "is invalid" clearly tells the user the email format is wrong.

3fill in blank

hard

Fix the error in the validation code to correctly validate a username with only letters and numbers.

Ruby on Rails

validates :username, format: { with: [1] }

Drag options to blanks, or click blank then click option'

A/[a-z]+/

B/[a-zA-Z0-9]/

C/\w+/

D/\A[a-zA-Z0-9]+\z/

Attempts:

3 left

💡 Hint

Common Mistakes

Using regex without anchors, allowing invalid characters.

Using \w+ which includes underscores.

The regex /\A[a-zA-Z0-9]+\z/ ensures the username contains only letters and numbers from start to end.

4fill in blank

hard

Fill both blanks to validate a phone number that must be exactly 10 digits.

Ruby on Rails

validates :phone, format: { with: [1], message: [2] }

Drag options to blanks, or click blank then click option'

A/\A\d{10}\z/

B"must be 10 digits"

C"invalid phone number"

D/\d+/

Attempts:

3 left

💡 Hint

Common Mistakes

Using a regex that matches any number of digits.

Using a vague or unrelated error message.

The regex /\A\d{10}\z/ matches exactly 10 digits, and the message clearly states the requirement.

5fill in blank

hard

Fill all three blanks to validate a password with at least 8 characters, including letters and numbers.

Ruby on Rails

validates :password, format: { with: [1], message: [2], allow_blank: [3] }

Drag options to blanks, or click blank then click option'

A/\A(?=.*[a-zA-Z])(?=.*\d).{8,}\z/

B"must include letters and numbers and be at least 8 characters"

Cfalse

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using a regex that does not check for both letters and digits.

Setting allow_blank to true, allowing empty passwords.

The regex ensures at least one letter and one digit with minimum length 8. The message explains the rule. allow_blank: false means password cannot be empty.

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