Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
RfC / DevCon 2015: Repository layer #81
The model classes have at the moment many tasks. At first they represent a row from the database.
Since the repository would have the same API as the model it would be probably easier to refactor.
Yes thats true and I think we should use the current orm layer. With "another layer" I meant that it should be possible to create a custom repository class which can provide a custom getObjectList/getObjectCount implementation. Maybe we should add a new annotation to the model class which reference the repository class of the model. Doctrine has the same approach to define a custom repository class for the model: