I think a case can be made for using an [EMAIL PROTECTED], @track] nested route -- say a user browsed to album 45, and then clicked track 219 -- if your UI requires a "back to album 45" navigational link on the track page, you couldn't infer the referring album id from the resource id alone if there's a many-to-many relationship between albums and tracks -- instead, you'd need to grab the album id from the URI.
On Jul 7, 11:04 am, Josh Peek <[EMAIL PROTECTED]> wrote: > On Jul 7, 10:59 am, Geoff B <[EMAIL PROTECTED]> wrote: > > > So, are you saying that, instead of doing this: > > > link_to @track.name, [EMAIL PROTECTED], @track] > > > ...we should be required to do this: > > > link_to @track.name, album_track_path(@album, @track) > > I'm saying you should be doing ... > > link_to @track.name, @track > > Like I said, [EMAIL PROTECTED], @track] is giving you an excuse to use complex > routing patterns. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
