we often use the pattern of scoping all of our controllers by objects that are not explicitly set as parents. This is a bit like the begin_of_association_chain method in inherited_resources (found: http://github.com/josevalim/inherited_resources/tree/master ).

a quick solution that we implemented is as follows:

in nested.rb

module ResourceController
 module Helpers
   module Nested
     protected 
      ....
    def scoped?
      scoping_object.present?
    end

    def scope_association
      @scope_association ||= scoping_object.send(model_name.to_s.pluralize.to_sym)
    end

    def end_of_association_chain
      return scope_association if scoped?
      parent? ? parent_association : model
    end
...
end

and then in the controller it is used as follows:

def scoping_object
   current_facility
end

This will scope all finds using current_facility.associations.find and create using
current_facility.associations.new

When I try: rescue_from ActiveRecord::RecordNotFound, :with => :something

The resource controller simply don't catch it, and it are returning a 200(ok) status when a record wasn't found.

It breaks my tests and my 404 handling.

Hi,

I use r_c 0.6.5 with Rails 2.3. According to the nested forms documentation, "object" within a nested fields_for block, when using nested forms, refers to the current child object. However, r_c seems to override this variable name globally for the complete template:

Whenever in my template, I do things like

<% form_for(@parent) do |form| %>
...
  <% form.fields_for :children do |child| %>
    <%= object.name %> is <%= object.age %> years old.
    <%= child.check_box :candy %> Allow more candy? <br/>
  <% end %>
...
<% end %>

I get an error

undefined method `name' for #<Parent:0x39fff44>

For me, this looks like r_c is overwriting the "object" variable since it obviously refers to the parent and not the current child within the block.

Can "object" within r_c be renamed or replaced easily? If anything just to debug this problem?
Thanks!

Jens

in /lib/resource_controller.rb
Lines:
begin
require_dependency 'application_controller' rescue LoadError => e
require_dependency 'application' end

The problem with this sort of check is that if you have a load error that has nothing to do with the application_controller v.s. application renamed dependency (say you defined a helper wrong etc.), then the true error is hidden and you get a no such file to load - application error instead.

To reproduce, use the latest rc as a plugin or a gem, create a model, controller, helper, etc. file and declare it wrong. I.e. post_help.rb but declared as "module OopsHelper". This is a pretty contrived example, but the point is, the way rc uses rescue on LoadError means your app hides any meaningful error messages that may occur on load, forcing you to edit rc and comment out those lines to figure out what the actual error was.