Well, this isn't my patch so I can't speak for the author, but when I added that feature to my plugin I did consider :as - but I discarded it because it didn't seem communicate exactly what would happen. If you didn't know about the feature and you saw:
map.resources :tutors, :as => :tutores You could reasonably assume tutores_path() was valid just as much as you could assume tutors_path() was valid. map.resources :tutors, :opaque_name => :tutores indicates (to me, anyhow) that something is unusual with :tutores - it sticks out like a sore thumb, prompting you to discover what that means. Regards, Trevor On 1/26/08, Xavier Noria <[EMAIL PROTECTED]> wrote: > > > On Jan 26, 2008, at 7:55 PM, Trevor Squires wrote: > > > One of my plugins has this feature and I call it :opaque_name. I > > chose 'opaque' because to me, that's exactly what it is - a name > > that doesn't let you "see through" to the underlying resource naming > > structure. > > > > map.resources :tutors, :opaque_name => :tutores > > tutors_path() => /tutores > > Why not just > > map.resources :tutors, :as => :tutores > > ? > > The id in a nested route is still tutors_id isn't it, internally there > are only tutors right? > > -- fxn > > > > > > > -- -- Trevor Squires http://somethinglearned.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
