This repository has been archived by the owner on Jul 3, 2020. It is now read-only.
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.
findBy(['property' => []])
is a feature available inEntityManager
only. Since you're typehintingObjectRepository
instead ofEntityManager
, is expected that this will work if you provide a MongoDB ODMDocumentManager
, which unfortunately does not happen given the lack of support for values in arrays.That said, i propose to use
Selectable
instead ofObjectRepository
, so it will be possible to use even aRole
Collection
to retrieve the Roles.This might seem very strange not to consider this a BC Break, but since you're typehinting
ObjectRepository
the expected behavior is already to work with any manager, and if this is not happening, i would consider this more a bugfix than a bc break. Also, the only possible working setting isEntityManager
, which is aSelectable
instance, so it will be perfectly compatible with any previous implementation.