I tend to agree with this. I don't really understand the need to "canonically" identify a resource based on its context.
Other thoughts? Evan > On 7/7/07, Josh Peek <[EMAIL PROTECTED]> wrote: > > > > I have a real grudge against the new nested polymorphic path magic > > stuff. I feel it encourages and gives people an excuse to write overly > > compelled routes. Resources should NOT be nested more than one level > > deep. > > > > "/companies/1/people/1" == BAD > > "/people/1" == GOOD > > > > I have no problem with nested collections. > > > > "/companies/1/people" > > > > You shouldn't need to be scoping person #1 if its the unique id. > > > > I've seen alot of defect and enhancement tickets going by Trac showing > > its immaturity and lack of real need. None of this stuff has been > > merge with the stable, so its not to late to change things. It should > > really be pulled from Edge and into a plugin, > > "nested_polymorphic_paths". > > > > Its not in the spirit of Rails to be providing tools to help you > > practice bad habits. > > > > > > > > > > > > > -- > Evan Weaver > Cloudburst, LLC > -- Evan Weaver Cloudburst, LLC --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
