I'm in the process of refactoring an existing Rails app and am
wondering - is it common practice to have a controller for each model
that has CRUD actions? For instance, in my app I have a side bar
where users can add diary entries to a side-bar, highlighting them in
bulletin-board fashion within their diary. This bulletin board will
only live inside the diary. Should it have its own controller then?
What's the general rule. I've been reading The Rails Way, and it
seems that it should, which would also allow me to create a nested
resource for this as well which would allow for some out-of-the-box
routing if I were ever to surface this component somewhere else.
I look forward to your thoughts, and thanks!