We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$container->set('Doctrine\ORM\EntityManager', $entityManager);
This will cause a problem because when the container will "getDefinition", there will be 2 incompatible definitions:
Doctrine\ORM\EntityManager
ClassDefinition
$entityManager
ValueDefinition
The solution would be that when a ValueDefinition exists, all other definitions are ignored.
The text was updated successfully, but these errors were encountered:
#70 Definition conflict when setting a value for a class name
b6e468f
When a ValueDefinition is found, all other definitions are ignored.
Fixed in 3.0.5
Sorry, something went wrong.
mnapoli
No branches or pull requests
This will cause a problem because when the container will "getDefinition", there will be 2 incompatible definitions:
Doctrine\ORM\EntityManager
class using Reflection ->ClassDefinition
$entityManager
instance ->ValueDefinition
The solution would be that when a ValueDefinition exists, all other definitions are ignored.
The text was updated successfully, but these errors were encountered: