Allow AbstractDoctrineExtension implementations to support the newer bu…

[fabpot]

Q	A
Feature PR	symfony/symfony#43181
PR author(s)	@mbabker
Merged in	5.4

[mbabker]

Someone can surely find a better way to describe this than me, but...

In the https://github.com/symfony/symfony-docs/blob/5.4/bundles/best_practices.rst#doctrine-entitiesdocuments section, when a bundle supports Symfony 5.4 (or, most specifically, the Doctrine Bridge at 5.4) and DoctrineBundle 2.5 (for ORM entities) or whatever version of DoctrineMongoDBBundle doctrine/DoctrineMongoDBBundle#713 lands in (for MongoDB ODM documents), the mapping files should be stored in config/doctrine. If supporting older versions of those dependencies, the Resources/config/doctrine path should still be used unless you want to deal with symlinks or manually register mapping paths.

That's probably the only change needed for the Symfony docs as the actual convention ends up being defined by a bundle or any implementation of AbstractDoctrineExtension and not the Doctrine Bridge itself.

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Friendly ping? Should this still be open? I will close if I don't hear anything.

[carsonbot]

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!