Most in the Rails community seem stick with 1 controller per resource
when using RESTfull routes.
This makes sense for a resource with one scope and one view, but once
a resource is used with multiple scopes and/or views the amount of
code duplication needed to manage these in a single controller can
balloon quick. Yet despite the impending chaos, it seems as though
people prefer to maintain a controller per resource.
Take these examples from Rails sites written by well respected
find_container() and find_events(): why would one want to do this?
This can become unmanageable. If each of these scopes require
different view components the same checks will have to be done in the
action's view or when determining the layout.
Look at how many times wall? and blog? have to be called. Not very DRY
if you ask me.
Rail's routing gives you these checks for free, why not create a
WallCommentsController and BlogCommentsController? If differing views
are involved for each of these it seems like a no brainer... but it's
never done. Why? What am I missing?