@@ -98,6 +98,21 @@ This can be easily handled using finder_filter: finder_filter :nested => :topic +Nested resources will only do a find on the parent model if the parent id is supplied. +This allows you to handle routing setups like this: + +map.resources :posts +map.resources :topics do |topic| + topic.resources :posts +end + +With this setup, both /posts/1 and /topics/1/posts/2 will be valid URLs, and will do the +right thing if you include + +finder_filter :nested => :topic + +in your Posts controller. + == from_param If you have Michael Bleigh's from_param (http://github.com/mbleigh/from_param/tree/master) README @@ -11,7 +11,7 @@ module FinderFilter define_method "find_#{name}" do klass = name.to_s.classify.constantize - if nested + if nested && params.include?("#{nested}_id") nested_klass = nested.to_s.classify.constantize nested_param = "#{nested}_id".intern lib/finder_filter.rb cf4afc34d14ed36b00343c4913196218d908ee11 Mike Gunderloy MikeG1@larkfarm.com http://github.com/ffmike/finder_filter/commit/a50fa6b92eb2190545a8b81ab95f0855e2202d0f a50fa6b92eb2190545a8b81ab95f0855e2202d0f 2008-09-06T09:01:27-07:00 2008-09-06T09:01:27-07:00 Make supplying parent id optional for nested finders. This supports routing such as: map.resources :posts map.resources :topics do |topic| topic.resources :posts end 4e44e67cd7f40dccea421d576a277568da181cfa Mike Gunderloy MikeG1@larkfarm.com