Controllers should have a single responsibility?

Question

As well as the classes and objects of an application, mine controllers should have a single responsibility?

Example.

I have my controller Cliente, who has all relations with my model Cliente.

I also have the model Contato.

It would be right for me to have mine actions ContatoPorCliente, ExcluirContatoCliente, etc. within my controller Cliente? Those actions are called in the view Cliente.

My question is why sometimes we have screens that have several Tabs(Tab) in a form. Client who has Contact, Financial Data, etc...

Answer 1

I see no problem in doing this, as long as the referred contacts have some relationship with the client, making explicit that they are a client’s contacts.

If there are other ways, other than through the client view, to manipulate contacts, then yes, I think the separation becomes more necessary.

You know, code organization patterns exist to help move the point in the project where the code is made... the separation of responsibilities predicts a need that usually comes to light during the maintenance phase (and that is a nightmare): the coupling, so it is better to make a code with low coupling degree from the beginning.

If contact is something that exists only as something that is part of the customer, then the coupling will not be high anyway... otherwise it is better to separate now.