On Sep 17, 3:15 pm, Josh Susser <[EMAIL PROTECTED]> wrote: > This is why I don't like overloading the comments= setter to handle > hashes, but prefer having a comments_params= setter instead. The > basic setter deals with models, the params setter is the convenience > interface for controllers to use for multi-model form support. It's a > much simpler implementation too.
Agreed, the setter method should have a different name than the existing "tasks=" method. The behavior is different enough to warrant its own method. Otherwise it will just be confusing on the implementation side and the API side. Is there any good reason for using the same setter method? Ryan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
