Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #20944 [HttpKernel] Fix Bundle name regression (ogizanagi)
This PR was merged into the 3.3-dev branch. Discussion ---------- [HttpKernel] Fix Bundle name regression | Q | A | ------------- | --- | Branch? | 3.2 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #20117 | License | MIT | Doc PR | N/A The bundle name can be set manually instead of being guessed from the class name, as the property is protected. However, a regression prevents this name to be used, as calling `Bundle::getNamespace()` recomputes the bundle name from class instead. The ability to name explicitly bundles is appreciable when dealing with "virtual" ones, or when providing bundles in a library under a `Vendor\MyPackage\Bridge\Symfony\Bundle` namespace. No need to rename the bundle class `VendorMyPackageBundle` which will make the instantiation in `Kernel::registerBundle()` quite ugly: ```diff - new Vendor\MyPackage\Bridge\Symfony\Bundle\VendorMyPackageBundle() + new Vendor\MyPackage\Bridge\Symfony\Bundle\Bundle() ``` What about removing `Bundle::parseClassName()` and processing the namespace and bundle name separately, but keeping the `namespace` property introduced in #20117? Commits ------- 3b5127d [HttpKernel] Fix Bundle name regression
- Loading branch information