Nested attributes in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when saving nested attributes with reject_if condition?

Consider a Rails model Order that accepts_nested_attributes_for :items with reject_if: :all_blank. What will be the result when saving an order with one item having all blank fields?

Ruby on Rails

class Order < ApplicationRecord
  has_many :items
  accepts_nested_attributes_for :items, reject_if: :all_blank
end

order = Order.new(items_attributes: [{name: '', quantity: ''}])
order.save
items_count = order.items.count

A The order saves and items_count is nil because items are not loaded

B The order saves and one blank item is created, so items_count is 1

C The order fails to save due to validation errors on items

D The order saves but no items are created, so items_count is 0

💡 Hint

Think about what reject_if: :all_blank does when nested attributes are blank.

The reject_if: :all_blank option prevents creation of nested records if all their attributes are blank. So the blank item is ignored, and no item is created. The order saves successfully with zero items.

📝 Syntax

intermediate

Which nested attributes syntax correctly updates a child record?

Given a Post model with many comments and accepts_nested_attributes_for :comments, which params hash correctly updates the comment with id 5?

Ruby on Rails

params = {
  post: {
    comments_attributes: {
      '5' => { content: 'Updated comment' }
    }
  }
}

A { post: { comments_attributes: { '5' => { content: 'Updated comment' } } } }

B { post: { comments_attributes: [{ content: 'Updated comment' }] } }

C { post: { comments_attributes: { id: 5, content: 'Updated comment' } } }

D { post: { comments_attributes: [{ id: 5, content: 'Updated comment' }] } }

💡 Hint

Remember that nested attributes for updating use a hash with keys as string ids.

When updating nested records, Rails expects a hash where keys are string ids of the child records. Option A matches this format. Option A uses an array which is for creating new records. Option A is missing the key structure. Option A lacks the id to identify which comment to update.

🔧 Debug

advanced

Why does this nested attribute update fail silently?

Given the following code, why does updating the nested profile of a User not change the profile's name?

Ruby on Rails

class User < ApplicationRecord
  has_one :profile
  accepts_nested_attributes_for :profile
end

user = User.find(1)
user.update(profile_attributes: { id: user.profile.id, name: 'New Name' })
user.profile.name

A The profile's name is not updated because the <code>profile</code> association is not marked as <code>autosave: true</code>

B The profile's name is not updated because <code>profile_attributes</code> is missing <code>allow_destroy: true</code>

C The profile's name is not updated because the <code>id</code> key is missing in the nested attributes

D The profile's name is not updated because the <code>profile</code> model has validations that fail silently

💡 Hint

Think about what Rails needs to save changes to associated records.

By default, has_one associations do not autosave changes to the associated record unless autosave: true is set. Without it, nested attribute updates to profile won't persist changes. The id key is present, and validations are not mentioned as failing.

❓ state_output

advanced

What is the state of child records after nested attributes update with _destroy flag?

Given a Project with many tasks and accepts_nested_attributes_for :tasks, allow_destroy: true, what happens after this update?

Ruby on Rails

project = Project.find(1)
project.update(tasks_attributes: [{ id: 10, _destroy: '1' }])
remaining_tasks = project.tasks.pluck(:id)

A The update fails because _destroy must be a boolean true, so remaining_tasks includes 10

B The task with id 10 is deleted, so remaining_tasks does not include 10

C The task with id 10 is marked as completed but not deleted, so remaining_tasks includes 10

D The task with id 10 is archived but still present, so remaining_tasks includes 10

💡 Hint

Recall what the _destroy flag does in nested attributes.

When allow_destroy: true is set, passing _destroy: '1' in nested attributes deletes the child record. So the task with id 10 is removed from the database and does not appear in the remaining tasks.

🧠 Conceptual

expert

Why use nested attributes instead of manual child record management?

Which is the best explanation for why Rails provides accepts_nested_attributes_for to handle nested attributes?

A It enforces database-level foreign key constraints to prevent orphaned child records

B It automatically validates all child records without needing explicit validation rules in child models

C It simplifies form handling by allowing parent and child records to be created or updated in one step, reducing manual code and errors

D It replaces the need for any callbacks or custom logic in models managing associations

💡 Hint

Think about the developer experience when working with forms that include related data.

accepts_nested_attributes_for allows a parent model to accept attributes for its associated child models in one form submission. This reduces the need for separate manual handling of child records, making code simpler and less error-prone. It does not automatically validate children or enforce database constraints, nor does it replace callbacks.