[DoctrineBridge] Add check for lazy object interface #53079
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Symfony 6.4 lazy loading of ghost proxies is the default. This means if using 6.4 components with the 5.4 version of the doctrine bridge you get the following error when trying to reset the entity manager: ``` Resetting a non-lazy manager service is not supported. Declare the "doctrine.orm.default_entity_manager" service as lazy. ``` The entity manager is set as lazy already in our case but it extends `\Symfony\Component\VarExporter\LazyObjectInterface` instead of the `LazyLoadingInterface`
maxbaldanza
commented
Dec 14, 2023
nicolas-grekas
approved these changes
Dec 19, 2023
Thanks @nicolas-grekas 🙌 |
stof
approved these changes
Dec 19, 2023
fabpot
approved these changes
Dec 19, 2023
|
Thank you @maxbaldanza. |
This was referenced Dec 30, 2023
Merged
Merged
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In Symfony 6.4 lazy loading of ghost proxies is used out of the box.
This means if using 6.4 components with the 5.4 version of the doctrine
bridge you get the following error when trying to reset the entity manager:
The entity manager is set as lazy
already in our case but it extends
\Symfony\Component\VarExporter\LazyObjectInterfaceinstead of theLazyLoadingInterfacethat's expected