How come there isn't (or if there is please point me to it) a repeatable pattern for consistently and safely enabling injection of a third party bundle's routing resource (/Resources/config/routing.yml) that happens "magically," similarly to the way to services.yml file is loaded in the FooBundle/DependencyInjection/AcmeFooExtension class's load method?
I understand that the "normal" practice is to just reference the bundle's routing resource in the application's routing.yml file ... but why can't it happen automagically?
I thought the reason might be that there could be route naming conflicts between multiple autoloaded bundles' routing files - but that could easily be resolved by some configuration parameters that would effectively insulate the different bundles' routes.
Appreciate the information.
