Re: Hatred towards Nested Polymorphic Paths

Josh Peek
2007-07-07T16:18:42Z

On Jul 7, 11:12 am, Geoff B <gbues...@gmail.com>
wrote:
> I think a case can be made for using an [@album, @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

If your referring to a HABTM relationship, look into creating a real
join model between them using has many though. That why you have a
real resource you can point your url to.