ivanpoval wrote in post #970446:
The code sample you provided is very common and many respectful Rails
developers use it.
If we go out of the scope of Rails and start speaking very strictly
about MVC, then probably we can say that it is not actually the
controller's job to do that type of things.
No. It *is* the controller's job to trigger render operations. There's
nothing un-MVC about this at all.
But I think that
render :update has its place in Rails also for a purpose.
I don't like render :update because I don't like RJS, but it's a
perfectly appropriate thing for the controller to do if all it's doing
is calling a partial.