I don't quite agree with your understanding of "repository". Imho it should NOT have application logic and also it is not in between something => it just adds another layer of abstraction to the data source.
Everything else is like I do it: I have a Business/Domain Object which uses Services to check/modify Repositories.
Langdi said:
I don't quite agree with your understanding of "repository". Imho it should NOT have application logic and also it is not in between something => it just adds another layer of abstraction to the data source.
Everything else is like I do it: I have a Business/Domain Object which uses Services to check/modify Repositories.
I meant CRUD on data source only, not validation or something.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community