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
Preload Autoloader class when the ORM is used #1167
Conversation
What about using a |
That's what I did first until I realized there is a condition on boot: The class is hit only when the ORM is used. |
Does this fix a bug in 2.0.x? Otherwise I'd opt to introduce this in 2.1.0 which will be released this week. |
Technically it does not a fix a bug, it's an improvement. But I need to take care of tests. |
In that case, let's push this into master. I didn't change the base (yet) as master seems to be missing an up merge from 2.0.x. Either way, let's try to get this into 2.1. Let me know if you need help |
6e4614d
to
116e1b5
Compare
116e1b5
to
b4c55dd
Compare
@@ -10,7 +10,7 @@ doctrine: | |||
memory: true | |||
|
|||
orm: | |||
default_entity_manager: dm2 | |||
default_entity_manager: default |
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.
The new logic above uncovered this error in the configuration. Looks like we don't check whether the default entity manager even exists 🤷♂️
Thanks @fancyweb! |
The
Autoloader
class is always used on bundle boot when the ORM is used.