Numericality validation in Ruby on Rails - Mini Project: Build & Apply

Numericality Validation in Rails Model

📖 Scenario: You are building a simple Rails application to manage products. Each product has a price that must be a number. To keep data clean, you want to ensure that the price is always a number when saving a product.

🎯 Goal: Learn how to add numericality validation to a Rails model attribute to ensure only numbers are accepted.

📋 What You'll Learn

Create a Rails model called Product with an attribute price

Add a numericality validation to the price attribute

Allow only numeric values for price

Ensure the validation is active when saving a product

💡 Why This Matters

🌍 Real World

Validations like numericality ensure that data entered into your app is correct and prevents errors later on.

💼 Career

Rails developers often add validations to models to enforce business rules and data integrity.

1

Create the Product model with a price attribute

Create a Rails model called Product with an attribute price of type decimal.

Ruby on Rails

# Create the Product model with a price attribute
# Your code here

Hint

Use rails generate model Product price:decimal to create the model and migration.

2

Add a numericality validation configuration

Inside the Product model, add a validation line that sets up numericality validation for the price attribute.

Ruby on Rails

class Product < ApplicationRecord
  # Add numericality validation for price
  # Your code here
end

Hint

Use validates :price, numericality: true inside the model class.

3

Test the numericality validation in the model

Write a method inside the Product model called valid_price? that returns true if the product is valid and false otherwise, using the built-in valid? method.

Ruby on Rails

class Product < ApplicationRecord
  validates :price, numericality: true

  # Define valid_price? method
  # Your code here
end

Hint

Use def valid_price? and inside it call valid? to check validations.

4

Complete the model with validation and method

Ensure the Product model includes the price attribute, the numericality validation, and the valid_price? method as defined.

Ruby on Rails

class Product < ApplicationRecord
  validates :price, numericality: true

  def valid_price?
    valid?
  end
end

# Model complete

Hint

Make sure all parts are present: class, validation, and method.

Practice

1. What does the validates :age, numericality: true line do in a Rails model?

easy

A. It checks if age is a string.

B. It makes the age attribute required.

C. It ensures the age attribute is a number.

D. It sets a default value for age.

Solution

1. Step 1: Understand numericality validation

   The numericality: true option checks if the attribute is a number.

2. Step 2: Apply to age attribute

   Since it is applied to age, it ensures age must be numeric.

3. Final Answer:

   It ensures the age attribute is a number. -> Option C

4. Quick Check:

   Numericality validation = ensures number [OK]

Hint: Numericality means the value must be a number [OK]

Common Mistakes:

• Confusing numericality with presence validation
• Thinking it sets default values
• Assuming it checks for strings

2. Which of the following is the correct syntax to validate that price is an integer in Rails?

easy

A. validates :price, numericality: { only_integer: true }

B. validates :price, integer: true

C. validates :price, number: { integer: true }

D. validates :price, numericality: true, integer: true

Solution

1. Step 1: Recall correct numericality syntax

   Rails uses numericality: { only_integer: true } to check integers.

2. Step 2: Check options

   validates :price, numericality: { only_integer: true } matches this syntax exactly; others are invalid or incorrect.

3. Final Answer:

   validates :price, numericality: { only_integer: true } -> Option A

4. Quick Check:

   Integer validation uses only_integer: true [OK]

Hint: Use only_integer inside numericality hash [OK]

Common Mistakes:

• Using a separate integer key instead of inside numericality
• Writing invalid keys like number or integer alone
• Missing curly braces for options

3. Given this model validation:

validates :score, numericality: { greater_than: 0, less_than_or_equal_to: 100 }

What happens if you try to save score = 150?

medium

A. Validation fails because 150 is greater than 100.

B. The record saves successfully.

C. Validation fails because 150 is less than 0.

D. Validation passes because 150 is a number.

Solution

1. Step 1: Understand validation limits

   The validation requires score to be greater than 0 and less than or equal to 100.

2. Step 2: Check the value 150

   150 is greater than 100, so it violates the less_than_or_equal_to: 100 rule.

3. Final Answer:

   Validation fails because 150 is greater than 100. -> Option A

4. Quick Check:

   Value must be ≤ 100, 150 fails [OK]

Hint: Check all numerical limits carefully [OK]

Common Mistakes:

• Ignoring upper limit and assuming number is valid
• Confusing greater_than with greater_than_or_equal_to
• Assuming any number passes

4. Identify the error in this validation:

validates :quantity, numericality: { only_integer: true, greater_than: 0, less_than: 10, message: 'must be a number' }

medium

A. There is no error; this validation is correct.

B. The message option is misplaced inside the numericality hash.

C. The validation is missing presence: true.

D. The only_integer option cannot be combined with greater_than.

Solution

1. Step 1: Check placement of message

   The message option should be outside the numericality options hash, not inside it.

2. Step 2: Validate other options

   only_integer, greater_than, and less_than can be combined correctly.

3. Final Answer:

   The message option is misplaced inside the numericality hash. -> Option B

4. Quick Check:

   Message option goes outside numericality hash [OK]

Hint: Put message outside numericality options hash [OK]

Common Mistakes:

• Placing message inside numericality hash
• Thinking only_integer conflicts with other options
• Assuming presence is required for numericality

5. You want to validate a rating attribute that must be an integer between 1 and 5 inclusive. Which validation code correctly enforces this?

hard

A. validates :rating, numericality: { only_integer: true, greater_than: 1, less_than: 5 }

B. validates :rating, numericality: { only_integer: true, greater_than: 1, less_than_or_equal_to: 5 }

C. validates :rating, numericality: { only_integer: true, greater_than_or_equal_to: 1, less_than: 5 }

D. validates :rating, numericality: { only_integer: true, greater_than_or_equal_to: 1, less_than_or_equal_to: 5 }

Solution

1. Step 1: Understand inclusive range requirements

   The rating must include 1 and 5, so use greater_than_or_equal_to: 1 and less_than_or_equal_to: 5.

2. Step 2: Check integer enforcement

   only_integer: true ensures rating is an integer.

3. Step 3: Compare options

   validates :rating, numericality: { only_integer: true, greater_than_or_equal_to: 1, less_than_or_equal_to: 5 } matches all requirements exactly; others exclude 1 or 5 or use wrong operators.

4. Final Answer:

   validates :rating, numericality: { only_integer: true, greater_than_or_equal_to: 1, less_than_or_equal_to: 5 } -> Option D

5. Quick Check:

   Inclusive integer range uses >= and <= [OK]

Hint: Use greater_than_or_equal_to and less_than_or_equal_to for inclusive range [OK]

Common Mistakes:

• Using greater_than or less_than excludes boundary values
• Forgetting only_integer for integer check
• Mixing up operators for inclusive range