Update TableLocator Interface to add more flexibility #14499
Closed
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.
Resolves #14495
This change creates more flexibility in the interface by allowing custom Locator implementations such as the use-case shown in #12014
It should actually make no difference to the core framework code as
\Cake\ORM\Table
already implements\Cake\Datasource\RepositoryInterface
.The only downside I can think of, might be the stand-alone ORM package, as I can't see the interface in there.