-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add lookup strategy to writer #11
base: master
Are you sure you want to change the base?
Conversation
bb7e615
to
cb38897
Compare
Wow you'r fast 😲 Good Job! |
Should we add a depreciation note somewhere? So we can remove this static constructur in the next major version? |
They are silenced, following the Symfony way: https://symfony.com/doc/current/components/phpunit_bridge.html#trigger-deprecation-notices
Added a (silenced) deprecation warning. |
* @param string $lookupMethod Method used for looking up the item | ||
* @param LookupStrategy $lookupStrategy | ||
* | ||
* @throws UnsupportedDatabaseTypeException | ||
*/ | ||
public function __construct( | ||
ObjectManager $objectManager, | ||
$objectName, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$objectName
needs to passed both here and when constructing a LookupStrategy
. Not very elegant, but I don’t see any other options now.
See #9 (comment).
Fix #3: if you want to use QueryBuilder, you can just implement your own
LookupStrategy
.