#436 √ wontfix
Chris

Implied routes to nested collections

Reported by Chris | June 17th, 2008 @ 05:54 AM

Often a resource is little more than a container for a nested collection. The tendency of applications lately is to use "pretty urls" to enhance the readability of a resource's URL. Additionally, it is quite common when performing search engine optimization to try to eliminate as many folders in the url path as possible. In such situations, it makes sense to collapse the primary path to a nested resource.

For example, consider a website with a local product where they list businesses by category, subcategory, state, city, and finally business name. The default url using nested routes would be:

/local/categories/restaurants/subcategories/korean/states/california/cities/mountain-view/totoro-tofu-house

However, all the types here can be assumed as long as the developer takes care to prevent the use of reserved names like "new" and "edit" resulting in a very pleasant and readable url like so:

/local/restaurants/korean/california/mountain-view/totoro-tofu-house

Having been faced with such requirements a number of times now, I became irritated that I couldn't use nested routes so I dug around in the resources code and found it not that hard to extend.

The result is a plugin for people to try this functionality located at:

http://github.com/caring/default...

And a patch to rails at:

http://github.com/chriseppstein/...

as well as attached.

This provides the ability for a resources declaration to declare itself as :default => true, thereby omitting the leading scope identifier. It also provides a :show => :foos that will delegate the show action of a nested resource to the index action of the FoosController by generating the show route with a lower routing priority than the nested index.

Comments and changes to this ticket

  • Chris

    Chris June 17th, 2008 @ 06:07 AM

    Sorry:

    "...delegate the show action of a nested resource to the index action..."

    Should have been:

    "...delgate the show action of a parent resource to the nested index action..."

  • Pratik

    Pratik August 21st, 2008 @ 12:13 PM

    • → Tag changed from “” to “actionpack enhancement patch routing”
    • → State changed from “new” to “wontfix”

    I think this is a better fit for a plugin. There are similar discussions going on in rails core mailing list. Probably you could express your opinions/suggestions there.

    Thanks.

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Source available from github

The Git repository resides at http://github.com/rails

Check out the current development trunk (Edge Rails) with:

git clone git://github.com/rails/rails.git

Creating or reviewing a patch

See the contributor guide.

Creating a feature request

Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.

Creating a bug report

When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.

Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".

Shared Ticket Bins

Attachments