The main purpose of this pattern is to have an extra-layer that would abstract away a particular Active Record ORM from the rest of the application. Repositories and entity managers are just parts of this bigger concept. This is actually written in Doctrine's documentation. The pattern it's based on is called Data Mapper. But first, Doctrine is not based on the Repository pattern.
Seems like you've missed the true purpose of this pattern. And this would be a big problem if, in Laravel, it was not so easy to test with the database.Īs we see in the following test, Laravel comes prepared to do this kind of automatic testing in a simple and clear way and, with Laravel Sail, we don't even have to worry about Docker containers. You can't test a simple class without having to mount a database, because there is no way to change or replace the model that is part of our domain code. Most of the time, when someone rejects active record is because it is not testable. In Laravel we have some good options to fix that. Me- True, but if that was your problem, you should have said earlier. Symfony dev- Well, even though we're increasing complexity and duplicating code, we can now mock the repository and run tests without accessing the database, and that's cool! Me- Have we gained anything, is there any difference between doing User::all() or doing $this->repository->all()? Enter fullscreen mode Exit fullscreen modeĪs we can see now we have encapsulated all the data access in a specific class, and we can stop using the model for this although, in reality, our model still has the same methods and the repository depends directly on it and that it has this inheritance with Eloquent.
0 kommentar(er)
