Form object pattern in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when the form object validates with invalid data?

Given a Rails form object that validates presence of a user's email and password, what will be the state of the form object after calling valid? with missing email?

Ruby on Rails

class UserForm
  include ActiveModel::Model
  attr_accessor :email, :password
  validates :email, presence: true
  validates :password, presence: true
end

form = UserForm.new(email: nil, password: 'secret')
form.valid?

A The form object raises an exception due to nil email.

B The form object is valid because password is present.

C The form object is invalid and errors include missing email message.

D The form object is valid but errors include missing email.

💡 Hint

Think about how ActiveModel::Model validations work when required attributes are missing.

The form object uses ActiveModel validations. Since email is missing, valid? returns false and errors include a message about email presence.

❓ state_output

intermediate

What is the value of user.name after form submission?

Consider a form object that assigns attributes to a User model on save. After calling form.save with name 'Alice', what is the value of user.name?

Ruby on Rails

class UserForm
  include ActiveModel::Model
  attr_accessor :name, :user

  def save
    return false unless valid?
    user.name = name
    true
  end
end

user = User.new(name: 'Bob')
form = UserForm.new(name: 'Alice', user: user)
form.save
user.name

A Raises NoMethodError

B 'Alice'

C nil

D 'Bob'

💡 Hint

Remember the form object assigns the name attribute to the user on successful save.

After form.save, the user's name is updated to 'Alice' because the form object assigns it before returning true.

📝 Syntax

advanced

Which option correctly defines a form object with nested attributes?

Which code snippet correctly implements a Rails form object that accepts nested attributes for an associated Profile model?

A

class UserForm
  include ActiveModel::Model
  attr_accessor :name, :profile_attributes
  validates :name, presence: true
  def save
    user = User.new(name: name)
    user.build_profile(profile_attributes)
    user.save
  end
end

B

class UserForm
  include ActiveModel::Model
  attr_accessor :name, :profile
  validates :name, presence: true
  accepts_nested_attributes_for :profile
  def save
    user = User.new(name: name)
    user.profile = profile
    user.save
  end
end

C

class UserForm
  include ActiveModel::Model
  attr_accessor :name, :profile_attributes
  validates :name, presence: true
  def save
    user = User.new(name: name)
    user.profile_attributes = profile_attributes
    user.save
  end
end

D

class UserForm
  include ActiveModel::Model
  attr_accessor :name, :profile_attributes
  validates :name, presence: true
  def save
    user = User.new(name: name)
    user.profile = Profile.new(profile_attributes)
    user.save
  end
end

💡 Hint

Remember that accepts_nested_attributes_for is a model method, not available in plain form objects.

Option D manually builds a new Profile with the nested attributes and assigns it to the user before saving. This is the correct way in a form object without model callbacks.

🔧 Debug

advanced

Why does this form object fail to save the user?

Given the following form object, why does this form object fail to persist the user even when valid data is provided?

Ruby on Rails

class UserForm
  include ActiveModel::Model
  attr_accessor :email, :user
  validates :email, presence: true

  def save
    return false unless valid?
    user.email = email
  end
end

user = User.new
form = UserForm.new(email: '[e-mail]', user: user)
form.save

A The save method does not call user.save, so changes are not persisted.

B The form object is missing a password attribute, causing validation failure.

C The user object is nil, so assignment fails with NoMethodError.

D The email attribute is not permitted, causing strong parameters error.

💡 Hint

Check if the user model is saved to the database after assignment.

The form object assigns the email to the user but never calls user.save. Without saving, changes are not persisted.

🧠 Conceptual

expert

What is the main benefit of using a form object pattern in Rails?

Why would a developer choose to use a form object instead of directly using ActiveRecord models in a Rails application?

A To separate complex form validation and business logic from the database models, improving code organization and testability.

B To automatically generate database migrations and schema from form inputs.

C To replace ActiveRecord models entirely and avoid using the database.

D To speed up page rendering by caching form data in memory.

💡 Hint

Think about how form objects help manage complexity in large applications.

Form objects encapsulate form-specific validations and logic separate from database models, making code cleaner and easier to maintain and test.

Practice

1. What is the main purpose of using a Form Object in Rails?

easy

A. To speed up database queries

B. To replace ActiveRecord models completely

C. To separate form validation and logic from database models

D. To generate HTML forms automatically

Solution

1. Step 1: Understand the role of form objects

   Form objects are used to keep form-related logic and validations separate from the database models.

2. Step 2: Compare with other options

   They do not replace ActiveRecord models or speed up queries, nor do they generate HTML forms automatically.

3. Final Answer:

   To separate form validation and logic from database models -> Option C

4. Quick Check:

   Form object purpose = Separation of form logic [OK]

Hint: Form objects separate form logic from models [OK]

Common Mistakes:

• Thinking form objects replace database models
• Assuming form objects speed up queries
• Confusing form objects with view helpers

2. Which module is commonly included in a Rails form object to provide model-like behavior?

easy

A. ActiveModel::Model

B. ActiveRecord::Base

C. ActionController::Base

D. ActiveSupport::Concern

Solution

1. Step 1: Identify the module for model-like behavior without DB

   The ActiveModel::Model module allows plain Ruby objects to behave like ActiveRecord models, including validations.

2. Step 2: Eliminate other options

   ActiveRecord::Base is for database models, ActionController::Base is for controllers, and ActiveSupport::Concern is for mixins.

3. Final Answer:

   ActiveModel::Model -> Option A

4. Quick Check:

   Form object module = ActiveModel::Model [OK]

Hint: Form objects include ActiveModel::Model for validations [OK]

Common Mistakes:

• Using ActiveRecord::Base in form objects
• Confusing controller modules with model modules
• Forgetting to include any module

3. Given this form object code, what will user_form.valid? return if email is blank?

class UserForm
  include ActiveModel::Model
  attr_accessor :email
  validates :email, presence: true
end

user_form = UserForm.new(email: '')
user_form.valid?

medium

A. true

B. false

C. nil

D. Raises an error

Solution

1. Step 1: Check validation rules

   The form object requires email to be present (not blank).

2. Step 2: Evaluate given input

   The email is an empty string, which fails the presence validation, so valid? returns false.

3. Final Answer:

   false -> Option B

4. Quick Check:

   Blank email fails presence validation = false [OK]

Hint: Presence validation fails on blank string [OK]

Common Mistakes:

• Assuming blank string passes presence validation
• Expecting valid? to raise error on blank
• Confusing nil and empty string behavior

4. Identify the error in this form object code:

class OrderForm
  include ActiveModel::Model
  attr_accessor :quantity
  validates :quantity, numericality: { greater_than: 0 }

  def save
    if valid?
      Order.create(quantity: quantity)
    end
  end
end

medium

A. Missing return value in save method

B. Order model is not defined

C. quantity is a string, needs conversion before validation

D. No error, code is correct

Solution

1. Step 1: Verify syntax and structure

   The code properly includes ActiveModel::Model, defines attr_accessor, and sets up numericality validation. Syntax is valid.

2. Step 2: Confirm behavior

   Numericality validation internally handles string-to-number conversion (e.g., '5' validates as > 0). The save method returns the Order instance (truthy) on success or nil/falsey otherwise, which works in conditionals.

3. Final Answer:

   No error, code is correct -> Option D

4. Quick Check:

   Numericality handles strings; save pattern acceptable [OK]

Hint: Rails numericality validator handles numeric strings automatically [OK]

Common Mistakes:

• Thinking strings need manual conversion for numericality
• Overthinking save method's return value
• Assuming undefined models cause errors in examples

5. You want to create a form object that handles user registration with email, password, and password_confirmation. Which approach correctly ensures password confirmation validation and saves the user if valid?

class RegistrationForm
  include ActiveModel::Model
  attr_accessor :email, :password, :password_confirmation

  validates :email, presence: true
  validates :password, presence: true, confirmation: true

  def save
    if valid?
      User.create(email: email, password: password)
    end
  end
end

hard

A. This code correctly validates and saves the user with password confirmation

B. Missing manual check for password_confirmation equality

C. Should use validates_confirmation_of :password_confirmation instead

D. Must call super in save method to save user

Solution

1. Step 1: Check validations for password confirmation

   The confirmation: true option on password automatically validates that password_confirmation matches.

2. Step 2: Verify save method logic

   The save method calls valid? and creates the user if valid, which is the correct pattern.

3. Final Answer:

   This code correctly validates and saves the user with password confirmation -> Option A

4. Quick Check:

   Password confirmation validation works with confirmation: true [OK]

Hint: Use confirmation: true for password confirmation validation [OK]

Common Mistakes:

• Manually checking password_confirmation equality
• Using deprecated validates_confirmation_of syntax
• Forgetting to call valid? before save