Great to hear! I brought the issue up because the params parser can only parse 2 levels deep before it gets screwed up and generates the wrong hash (I guess this all depends on the hash structure that is ultimately decided on for nested mass-assignment).
I also agree that enabling this manually makes a lot of sense for security purposes. Brad On Sep 15, 4:22 pm, Ryan Bates <[EMAIL PROTECTED]> wrote: > On Sep 15, 11:38 am, Brad Gessler <[EMAIL PROTECTED]> wrote: > > > Are there any plans to allow this type of attribute nesting to go > > beyond just 2 levels deep? > > Yes, in a sense that comes "for free" because we're just doing mass > assignment in the nesting. You can go as deep as you want as long as > it's supported through mass assignment. This is one reason why this > feature should need to be enabled manually instead of always on by > default (for security). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
