Can you please tell me how architecturally correct it is in the context of ZF2 (3) to extend the framework classes through inheritance?

For example, the Mvc class of the controller, module, ViewResolver class, Manager classes (Service, Module, Event), ORM classes.

Why the question arises: In ZF1, this was the standard way of tuning the framework - there were no alternatives to the tunne framework, plus the fact that through inheritance it was very convenient to make “your own framework”. In ZF2, there is an event system - everything is done through events; through the interception of events, you can radically change the work of most components, including the kernel components.

An alternative appears - where it is possible: to use events, where there is no - inheritance. But this does not look entirely correct from the point of view of OOP, and it is more habitual to solve everything through inheritance than to understand the events of the kernel of the zend and the order of their execution. Which way will the project be more flexible, and will seniour-programmers work with it easier?

Closed due to the fact that it is necessary to reformulate the question so that you can give an objectively correct answer to the party PashaPash 2 Oct '16 at 8:42 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

    0