Fix deprecations and ensure compatibility with Symfony 6.4 (#420) for…

[joscraw]

Fix deprecations and ensure compatibility with Symfony 6.4 (#420)

• Updated SymfonyFixturesLoader to conditionally set the container:

  • Added a class_exists check for ContainerAwareInterface in the addFixture method.
  • Passed bool and ContainerInterface to the constructor of SymfonyFixturesLoader.

• Updated DoctrineFixturesExtension for future compatibility:

  • Added ?ConfigurationInterface return type to getConfiguration method.
  • Replaced HttpKernelExtension with Symfony\Component\DependencyInjection\Extension\Extension.

• Fixed tests to correctly initialize SymfonyFixturesLoader:

  • Updated LoadDataFixturesDoctrineCommandTest to pass correct parameters to SymfonyFixturesLoader.

• Implemented isUninitializedObject method in EntityManagerDecorator for future Doctrine compatibility.

These changes address deprecation warnings and ensure compatibility with Symfony 6.4 and future versions.

[craigh]

bump 🤜

[greg0ire]

It seems there are CI jobs failing. Please take a look at this guide for more on how to handle those.

[craigh]

@joscraw any chance you can update this to fix the failing jobs?

[joscraw]

@craigh Hey guys! Sorry, I was out for a bit. Yup I'm on it! I'll take care of it here in a few min.

[stanislav-oop]

Thank you! When do you think it will be merged?

[stanislav-oop]

I am reviewing the depreciations (LTS symfony 6.4) and I can see the depreciation is coming from just the doctrine fixtures without any other custom code. Can not find any other workaround.

[derrabus]

Can not find any other workaround.

Does that fix the deprecations for you?

"doctrine/doctrine-fixtures-bundle": "^4@dev"

[stanislav-oop]

Yes it does, but for the minimum-stablity

[derrabus]

the minimum-stablity

That's fixable on our side. 🙉

@greg0ire @SenseException Shall we release 4.0?

[greg0ire]

Sure!

[joscraw]

@derrabus Releasing the 4.0.x branch instead def makes more sense to me! Thanks guys!