I was working on a resources-related patch recently and came across an implementation question...
When mapping resources with has_one associations, the has_one association is modeled by the map_associations method as a singleton resource. I thought that a singleton resource was supposed to be global to the application's current user. has_one's are not global to the user, they're global to the resource they belong to. This also has the (I think) unintended effect of looking for a single named controller. For instance: map.resources :products, :has_one => :manufacturer will look for a ManufacturerController not a ManufacturersController. If I wish to access the manufacturers resource outside of the context of this association, I'll need to add a ManufacturersController as well. Shouldn't has_one associations be mapped the same way has_many associations are? or am I just not understanding the implementation chosen? Thanks, Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
