Currently, attempt to register a bundle with a name that is already in _named_bundle will raise a RegisterError if a new bundle is not the same, as the previous one. Generally, it doesn't create any problem, but for rare cases of systems with the ability to replace themes/assets on-the-fly, it can be a grave thing. Maybe it has sense either to use warnings for such cases or provide an additional argument to register or add a flag to Environment with an explicit mark that re-registration is allowed/forbidden?
Currently, attempt to register a bundle with a name that is already in
_named_bundlewill raise aRegisterErrorif a new bundle is not the same, as the previous one. Generally, it doesn't create any problem, but for rare cases of systems with the ability to replace themes/assets on-the-fly, it can be a grave thing. Maybe it has sense either to use warnings for such cases or provide an additional argument toregisteror add a flag toEnvironmentwith an explicit mark that re-registration is allowed/forbidden?