Closed aschempp closed 7 years ago
If the legacy modules in Contao\ModuleLoader would be a constant instead of a private method, we would not have to re-define these again in the ModuleConfig. I suggest to make that change, it cannot be a BC break.
I don't think that's needed here, really. It's something that's never gonna change so it's not needed to be fetched "dynamically". Just leave it as is, imho.
If the legacy modules in Contao\ModuleLoader would be a constant instead of a private method, we would not have to re-define these again in the ModuleConfig. I suggest to make that change, it cannot be a BC break.
I don't think that's needed here, really. It's something that's never gonna change so it's not needed to be fetched "dynamically". Just leave it as is, imho.
I don't care either way. I think @Toflar is right though.
fine with me :-)
If a module in
system/modules
does currently not have anautoload.ini
, the sorting of dependencies gets wrong because the original core modules no longer exist so the sort-by-name no longer applies.This PR restores at least the functionality to request sorting before the legacy core modules. Having an
autoload.ini
would automatically override these defaults.Open question: If the legacy modules in
Contao\ModuleLoader
would be a constant instead of a private method, we would not have to re-define these again in theModuleConfig
. I suggest to make that change, it cannot be a BC break.