When I first saw nested resources in this REST paper I thought cool that makes sense. So we started using the nested resource method in our projects. Then it got a bit wierd – like why should I have to do this/1/that/2/foo/3 if I want to get to foo. Why can’t I just get to foo/3. Then I read that Jamis felt the same way.
So then I fell in love with Edge Rails and found out that the :has_many and :has_one methods have found their way into routes. (Here’s the change.) This is very cool so I threw it in, but I could get the helper methods to work (stuff like entries_path(@feed) stopped working. I don’t know why but I just have a heck of a time figuring out the helper methods, but they are worth using. For example future versions of Rails will replace ‘;’ with ‘/’ in their restful routes. If you hard coded the ‘;’ you now have to go back and change it. You should have used the helper methods.
Anyway, I found Changes to Nested Resource Routes to be a grand helper when figuring out the new helper methods.