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.