Add lookup strategy to writer - #11
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. |
| */ | ||
| public function __construct( | ||
| ObjectManager $objectManager, | ||
| $objectName, |
There was a problem hiding this comment.
$objectName needs to passed both here and when constructing a LookupStrategy. Not very elegant, but I don’t see any other options now.
|
Superseded by a 2.x port: #31 The original branch cannot be rebased cleanly onto current master (CONFLICTING; PHP 8.2 / doctrine/persistence modernization). PR #31 reimplements the LookupStrategy idea with BC-safe defaults and fixes several issues in this branch (missing Recommendation: close this PR once #31 is reviewed (do not merge this 2017 branch). |
Additive 2.x port of lookup strategies with tests; BC defaults preserved.
|
Superseded by #31 (merged), which reimplements lookup strategies for the 2.x line with tests and green CI. The 2017 branch could not be rebased cleanly; not merged as-is. Thanks for the original design. |
See #9 (comment).
Fix #3: if you want to use QueryBuilder, you can just implement your own
LookupStrategy.