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

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

Comments

Projects
None yet
1 participant
@mnapoli
Member

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

This comment has been minimized.

Show comment
Hide comment
@mnapoli

mnapoli Jun 11, 2013

Member

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

Fixed in 3.0.5

Member

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