-
Notifications
You must be signed in to change notification settings - Fork 103
ObjectMetadataResolver::loadObjectManager not supporting Doctrine\ORM\EntityManager #130
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
Comments
My theory is that this is caused by doctrine/persistence 2.0. Please check that the code works if you stay on |
This was the correct answer. Thank you. |
Just pushed the right solution to dev-master: b43fe3e Can you test that it works with whatever version of doctrine/persistence you want to use? Thanks :) |
@ondrejmirtes then I would suggest bumping |
@mente Why? What error message are you seeing? |
Wow, thanks for prompt reply! TL;DR I can't use
And following <?php
require dirname(__DIR__) . '/app/autoload.php';
require dirname(__DIR__) . '/app/AppKernel.php';
require dirname(__DIR__) . '/app/bootstrap.php';
$kernel = new AppKernel('dev', false);
$kernel->boot();
return $kernel->getContainer()->get('doctrine')->getManager(); I get following error:
|
if you're willing to support orm 2.5 I can try to find a possible options how to fix it and provide PR |
I see, I haven't thought of this. I thought that declaring conflict with |
Alternatively, you can lock in an older version of phpstan/phpstan and phpstan/phpstan-doctrine - phpstan/phpstan 0.12.25 and phpstan/phpstan-doctrine 0.12.13 work together. |
Sure thing, just wish it was that easy :). Wanted to point out the disrepancy between phpstan dependencies in |
I wasn't aware of this problem, I'll add a conflict :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
object-manager.php:
getEM()
method:Returning an EntityManager worked previously. Was something changed to make this incompatible?
The text was updated successfully, but these errors were encountered: