Introduce EntityRepositoryInterface, ancestor for custom repositories #6871
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introducing a common ancestor for custom repositories.
Currently there is a slight mess, some pieces of code only specify ObjectRepository which:
a) is insufficient since it's missing Selectable;
b) is incorrect since following code expects EntityRepository.
I've taken the opportunity to also add return types to the interface and default repository. Also updated some phpDocs - specialized
array
and removed duplicate information.This change should not affect 99.9% of user code since almost everyone extends EntityRepository, but allows 1% to use custom repositories in fancier way.
TODO: