> Given that has_many: associations are not even marshalled to XML unless you > specifically ask for them - I wonder how many folks are really using the > current behaviour. So I'd personally prefer the default behaviour change - > rails should do the right thing by default - and we keep the old behaviour > as an option folks can enable if they really want.
Ok, I'm sold. If we change the default behaviour to use the association name, and provide an option to retain the old behaviour then people who rely on the current stuff (think @section.to_xml :include=>:published_posts) can retain it. > Incidentally I really hate the option name I picked of :polymorphic but > every other option I considered seemed too long. Maybe we need options like > :use_association_name_for_many or :use_first_type_name_for_many (depending > on which is the default and which has to be enabled)? I'll have a think about a decent name for this 'use first type name for collection' option, but if anyone else wants to chime in with the perfect solution, now's the time :). -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
