Skip to content
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

Definition conflict when setting a value for a class name #70

Closed
mnapoli opened this issue Jun 11, 2013 · 1 comment
Closed

Definition conflict when setting a value for a class name #70

mnapoli opened this issue Jun 11, 2013 · 1 comment
Assignees
Labels
bug

Comments

@mnapoli
Copy link
Member

@mnapoli mnapoli commented Jun 11, 2013

$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 class using Reflection -> ClassDefinition
  • $entityManager instance -> ValueDefinition

The solution would be that when a ValueDefinition exists, all other definitions are ignored.

@mnapoli
Copy link
Member Author

@mnapoli mnapoli commented Jun 11, 2013

When a ValueDefinition is found, all other definitions are ignored.

Fixed in 3.0.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.