support for nested attributes with dynamic number of elements

[pkmiec]

Rebased as one commit.

Since the validations for each nested attribute are the same, there is no need to have them repeated for each model. Instead, the validations can be specified once for all the nested attributes and then applied to fields at any index.

For example, given users that accepts nested attributes for emails, the form will contain the following fields,

user[email_attributes][0][email_address]
user[email_attributes][1][email_address]
user[email_attributes][2][email_address]
user[email_attributes][N][email_address]

we can specify validation for all email_address fields simply as,

user[email_attributes][][email_address]

This not only sends less data to the client but also works with dynamic forms (i.e. press + to add another email address field).

[astjohn]

This is a great addition that works for my dynamic fields. Thanks!

[pkmiec]

Cool.

I'm not really sure what's holding up the pull request, though.

[bcardarella]

I've been busy and haven't had the time to review the pull request, sorry.

[pkmiec]

Thanks for the update.

[bcardarella]

@pkmiec I'm very sorry I let this go stale. Can you please rebase so I can merge?

[pkmiec]

@bcardarella rebased ... there are test failures but the same failures occur on master.

[kstevens715]

This sounds like what I need too. I'm using Cocoon to dynamically add nested fields and the validations aren't being performed. The validation is a custom, remote validation. Interestingly, even when I'm editing a pre-existing object with nested objects already added the validations still aren't being performed. However, if I try and set the same validation on a top-level attribute, the validation works perfectly.

I'm hoping this will solve my problem and maybe I'll just wait until there's an update before worrying about it.

[bcardarella]

Totally forgot about this, merged in.