re: Getting Familiar With The Awesome Repository Pattern VIEW POST


I would say that the CompanyLogic class should not know about two different models or sets or whatever you call it. You could split that into two different classes like PersonCompanyLogic and CompanyLogic each in charge of their own models.


That is a great suggestion Ivan and I agree. Separate logic layers is common but it is usually based on the logic behavior.

Code of Conduct Report abuse