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.
CompanyLogic
PersonCompanyLogic
That is a great suggestion Ivan and I agree. Separate logic layers is common but it is usually based on the logic behavior.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would say that the
CompanyLogicclass should not know about two different models or sets or whatever you call it. You could split that into two different classes likePersonCompanyLogicandCompanyLogiceach 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.