Fix deprecation on load fixtures command

[yceruto]

  1x: The "Doctrine\Bundle\FixturesBundle\Command\LoadDataFixturesDoctrineCommand" constructor expects a "Doctrine\Common\Persistence\ManagerRegistry" instance as first argument, not passing it will throw a \TypeError in DoctrineBundle 2.0.
    1x in Application::run from Symfony\Bundle\FrameworkBundle\Console
  1x: The "Doctrine\Bundle\DoctrineBundle\Command\DoctrineCommand::getContainer()" method is deprecated and will be removed in DoctrineBundle 2.0.
    1x in Application::run from Symfony\Bundle\FrameworkBundle\Console

[alcaeus]

One more suggestion, other than that, this looks good 👍

[alcaeus]

Thanks @yceruto!

[yceruto]

@alcaeus Is there a plan to release a new version to get rid of this warning everywhere? Thank you.

[alcaeus]

I’ll take time to do some housekeeping in the bundle next week 👍

[alcaeus]

3.2.0 is released. Thanks @yceruto!

[fsevestre]

Hello,

The Symfony Command constructor argument is waiting for a string and not an object. https://github.com/symfony/symfony/blob/4.4/src/Symfony/Component/Console/Command/Command.php#L69

On previous SF versions (without PHP 7 type), it breaks here (https://github.com/symfony/symfony/blob/3.4/src/Symfony/Component/Console/Command/Command.php#L660), which is calls by the setName.

Running bin/console --env=test for example returns

In Command.php line 659:
                                                                        
  Warning: preg_match() expects parameter 2 to be string, object given

[alcaeus]

Please use 3.2.2 which fixes this. Thanks!