nested attributes / nested form and draper followup about draper

[tmaier]

It seems like this bug is not related to nested_form. It's related to ActionView.

When using draper, fields_for does not set the :child_index (as called by nested_form in line 25).

FormHelper uses and sets the child_index in https://github.com/rails/rails/blob/master/actionpack/lib/action_view/helpers/form_helper.rb#L1398-1415

I added some debug calls for the method fields_for_with_nested_attributes and this is the result:

start fields_for_with_nested_attributes for new_phones
  respnds to persisted
    before line 1403: #<Phone:0x000001026e9120>
    after line 1403:  #<Phone:0x000001026e9120>
  respond_to?(:to_ary)
    nay!
start fields_for_with_nested_attributes for new_emails
  respnds to persisted
    before line 1403: #<Email:0x00000102539ac8>
    after line 1403:  [#<Email _id: 4ede6477499dda1d14000006, _type: nil, type: "Work", email: nil, status: nil>]
  respond_to?(:to_ary)
    yay!

phones and emails have exactly the same relation (mongoid, embeds_many), but to different Models. phones uses PhoneDecorator and emails Email.

This means the call to

association = [association] if @object.send(association_name).is_a?(Array)

in line 1403 fails.

[steveklabnik]

Is this still an issue now that that pull request has been merged in?

[tmaier]

No. Thanks for merging!

[steveklabnik]

w00t!