Deprecate extension via Doctrine Event Manager#5786
Conversation
afcfcaf to
10988f8
Compare
10988f8 to
5342f04
Compare
UPGRADE.md
Outdated
| - `AbsractPlatform::$_eventManager`, | ||
| - `AbsractPlatform::getEventManager()`, | ||
| - `AbsractPlatform::setEventManager()`, |
There was a problem hiding this comment.
| - `AbsractPlatform::$_eventManager`, | |
| - `AbsractPlatform::getEventManager()`, | |
| - `AbsractPlatform::setEventManager()`, | |
| - `AbstractPlatform::$_eventManager`, | |
| - `AbstractPlatform::getEventManager()`, | |
| - `AbstractPlatform::setEventManager()`, |
5342f04 to
cc8a35e
Compare
|
Hi, I use in my test the following code When i'm creating a custom entityManager, because I use doctrine-extensions: Does this deprecation means that all the listener from doctrine-extensions will be rewritten ? Or is there another way to set them manually ? |
|
That listener does not listen on any DBAL events, so you won't have a problem. |
My test are failing if I remove thought. And since the latest version, I get a phpstan error since it turns out that is working, without any deprecation. So I'll do this way, but I dunno why the difference and why one way was deprecated. |
|
You retrieved the event manager from the database connection to register event listeners for the entity manager. That does not sound like a good idea, does it. |
$this->entityManager->getConnection()->getEventManager()vs. $this->entityManager->getEventManager() |
|
Oh I see. Thanks |
Closes #5784.