Comments on: Rails: Nested resource scaffold

By: Santiago GL

Santiago GL — Sun, 23 Dec 2007 17:32:13 +0000

I am using Rails 1.2.4.
When recipes_controller.rb does NOT exist, the mapping to /recipes/1/ingredients does show the ingredients that belong to recipe 1.
That’s ok!
But when recipes_controller.rb DOES exist, the nested resource (/recipes/1/ingredients) outputs

Unknown action \ No action responded to 1

If I call /recipes/1.xml/ingredients it outputs a routing error, that is, there is no route to that resource.
What am I doing wrong?
Thanks

By: Ariejan de Vroom

Ariejan de Vroom — Wed, 12 Dec 2007 06:45:37 +0000

@Brian: Just like you nested ingredients into recipes, you can nest recipes in books. Note that this means that you’ll have to use books_recipe_ingredients_url(@book, @recipe, @ingredient))

You can do this. But if you stuff the same recipies in different books, I wouldn’t nest ‘em.

Good luck with your app.

By: Brian

Brian — Tue, 11 Dec 2007 22:13:07 +0000

What if recipes where in books. so you wanted book/:id/recipe/:id/ingredients
How would the route.rb look then – can you double nest or should you just not do this? We have a lot of these situations.

By: matthijs

matthijs — Fri, 31 Aug 2007 09:24:20 +0000

oops the code in my comment should be:
url_for([@matter.client, @matter]) do |f|

By: Matthijs

Matthijs — Thu, 30 Aug 2007 16:22:50 +0000

brandon wrote:

… Having a slight issue with the _path that is being created. I have a Client that has_many Matters. On my show page for my client I built in a form for adding new matters. The form has: matters_path(@client, @matter)) do |f| %> which builds the url /matters/ rather than /clients/1/matters/ which is what I need for the proper save. Any advice?

I have been working on this same issue today the solution I found was
url_for([@cient.matter, @matter]) do |f| -%>
This generates the expected post URL /client/:client_id/matters so the controller can user the params[client_id] to scope the new matter to the correct client!

hope this helps

By: Ben Wyrosdick

Ben Wyrosdick — Tue, 22 May 2007 18:47:57 +0000

I guess the new stuff in trunk is to address problems like joost was having. that way it separates the calls to all recipes ingredients_path & recipe_ingredients_path(@recipe).

By: Shane Vitarana

Shane Vitarana — Wed, 09 May 2007 19:04:43 +0000

Just wanted to mention that in the latest Rails trunk, you have to prefix a nested resource with its parent. So ingredient_path(@recipe, @ingredient) will become recipe_ingredient_path(@recipe, @ingredient).

By: Thomas Ritz » Blog Archive » Rails REST routes explained

Thomas Ritz » Blog Archive » Rails REST routes explained — Sat, 21 Apr 2007 11:40:13 +0000

[...] has another post that concentrates on nested [...]

By: Ariejan

Ariejan — Mon, 19 Mar 2007 22:17:12 +0000

@joost: Just add map.resoureces :ingredients to your config/routes.rb

You’ll have ingredients twice there, but that’s no problem at all. I was amazed by this too when I found out, but it works perfectly.

By: joost baaij

joost baaij — Mon, 19 Mar 2007 12:11:55 +0000

I agree that nested routes are a thing of beauty, but once nested it seems impossible to ‘un-nest’ a resource.

What I am getting at is that I would like to

a) show the ingredients for one recipe. this works fine.

b) show a list of ingredients covering all recipies.

This latter doesn’t seem possible. Logically, the url would become /ingredients but these can only exist inside recipes (giving /recipes/2/ingredients).

Do you know a way to have both? List all ingredients for one recipe AND list them all for all recipes?