I’ve seen this DHH article (Organizing Controllers a la DHH) where he organizes non-CRUD methods in a separate controller. This somehow I can understand the rationale.
However, I’m working on this project which is at its infancy stage. And I’m seeing this for the first time:
controllers/ topics/ topics_controller.rb posts/ posts_controller.rb
So you can imagine namespaces such as Posts::PostsController and etc. Routes riddled with nested
scope modules: <resource>
I asked the reason why we’re doing it like this, and the argument is to keep things organized.
I’m always a proponent of simple engineering and unnecessary abstractions. To have messy routes and protracted namespaces is too much just to keep things organized or maybe I’m just lacking experience in Rails and this is a thing already and I’m behind the times.
So with that being said, what are your thoughts? And how do you do (organize) yours?