Review Checklist

• Target branch (11.5 for bug fixes, others 11.x)
• Tests (if it's testable code, there should be a test for it - get help)
• Docs (every functionality needs to be documented, see here)
• Migration incl. install.sql (e.g. if the database schema changes, ...)
• Upgrade notes (deprecations, important information, migration hints, ...)
• Label
• Milestone

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

I have read the CLA Document and I hereby sign the CLA

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Thx very much for your contribution.

But, I'm not sure how \App\Bundle\MyBundle and \App\Bundle\MyOtherBundle could be distinguished by adding a bundle separator?

My bad, you're right in that case. But if we had \App\Bundle\CustomManagementBundle and \App\Bundle\CustomOrganizationBundle, we see that both namespaces start with \App\Bundle\Custom, thus both would match.

And how does a namespace separator help in this case?

Sorry, good point. Now I have the proper example:
We have

\App\Bundle\Branding\BrandingBundle // namespace: \App\Bundle\Branding
\App\Bundle\BrandingAdmin\BrandingAdminBundle // namespace: \App\Bundle\BrandingAdmin

If you then want to resolve: \App\Bundle\BrandingAdmin\Document\MyBrick using str_starts_with, both namespaces above would match.

thx for clarification.