\Magento\Framework\Config\Reader\Filesystem::_createConfigMerger() uses the «new» keyword instead of the Object Manager even after the Object Manager has already been initialized, so it breaks a dependency injection possibility

dmitry_fedyuk · November 15, 2015, 5:13am

magento/magento2/blob/2335247d4ae2dc1e0728ee73022b0a244ccd7f4c/lib/internal/Magento/Framework/Config/Reader/Filesystem.php#L173-L179


      
          $result = new $mergerClass(
              $initialContents,
              $this->validationState,
              $this->_idAttributes,
              null,
              $this->_perFileSchema
          );

See also Magento 2 ignores XML schema location in the etc/adminhtml/system.xml documents and always uses the Magento/Config/etc/system_file.xsd schema instead

dmitry_fedyuk · November 15, 2015, 5:54am

A partial solution for my particular case: How to change a constructor argument’s value with the depenency injection.

dmitry_fedyuk · July 31, 2023, 7:55pm

It is still not fixed in Magento 2.4.7-beta1:

github.com

magento/magento2/blob/2.4.7-beta1/lib/internal/Magento/Framework/Config/Reader/Filesystem.php#L209-L209


      
          $result = new $mergerClass(