Raymond O’Connor wrote:
Thanks for the help so far. Here’s a more concrete example of what I’m
talking about. I have an app used for warehousing and fulfillment.
Some of the controller domains are:
Shipping Out Items
Finance Related Stuff
Within just the Receiving controller there are dozens of view files
because it’s become larger and larger over the years. You need to be
able to receive a shipment, then receiving individual items in a
shipment, track exception cases, edit previous check in data, etc. I’d
really like a way to organize some of those files such that I have
All my controllers are getting to this size or are already there. I was
just wondering if there was an easy way to refractor and organize
projects of these size.
Your controllers are far too big and general. Receiving should not be
one controller. You’d probably want a ShipmentsController, an
ExceptionCasesController, and so on.
You could probably benefit from redesigning your controllers to follow a
RESTful pattern. You needn’t adhere slavishly to it, but using REST as
a guideline will give you a better idea of what controllers are normally
expected to do.