There’s nothing inherently wrong with multiple models in a
controller. Often times, though, you’re dealing with a single model
and its associations (which are other models). For instance, finding
a product and its category, brand, sizes, and colors. You only need: @product = Product.find(params[:id]) to get @product.brand, @product.category, @product.sizes, etc.
I find it better, even though multiple controllers do very much the same
thing, to have a separate controller for every model in the case that if
have to change something in one model I don’t have to split it up later
It’s also more along the lines of the Rails way.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.