Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feature #43181 Allow AbstractDoctrineExtension implementations to sup…
…port the newer bundle structure (mbabker) This PR was merged into the 5.4 branch. Discussion ---------- Allow AbstractDoctrineExtension implementations to support the newer bundle structure | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | no | New feature? | yes | Deprecations? | yes | Tickets | N/A | License | MIT | Doc PR | TBD Container extensions inheriting from `Symfony\Bridge\Doctrine\DependencyInjection\AbstractDoctrineExtension` (i.e. the extensions in all Doctrine bundles) currently cannot smoothly support the newer bundle directory structure because the existing API relies on information being gleaned from Reflection for the bundle class. This PR is an attempt to allow these extensions to support the newer structure. The notable changes here are: - The `getMappingDriverBundleConfigDefaults()` method adds a `string $bundleDir` argument which replaces gleaning the bundle directory by reflecting on the Bundle class - The abstract `getMappingResourceConfigDirectory()` method adds a `string $bundleDir` argument, this is needed for the concrete implementations to have conditional paths supporting both structures (similar to other checks in the framework like the `is_dir($bundleDir.'/Resources/views') ? $bundleDir.'/Resources/views' : $bundleDir.'/templates'` check for the templates path) Commits ------- 136c4a3 [DoctrineBridge] Allow AbstractDoctrineExtension implementations to support the newer bundle structure
- Loading branch information
Showing
4 changed files
with
30 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters