[Bug?] \Magento\Framework\App\Config::getValue() behavior is inconsistent with Magento 1.x Mage::getStoreConfig() method

[dmitrii-fediuk]

Magento 2 by default returns a config option value for the default scope while Magento 1.x by default returns a config option value for the current store scope.
A detailed analysis here: https://mage2.pro/t/128
May be it is assumed but it looks like a bug and I do not understand the reason why the behavior was changed.

[adragus-inviqa]

Being different than M1 does not make it a bug, but I whole-heartedly agree that the default scope should not be DEFAULT, but STORE.

The lowest scope should be used, as that's what usually people want. Besides, I think the STORE scope falls back to DEFAULT anyway, whereas DEFAULT doesn't.

LE:
phpstorm tells me it found some ~1300 uses of \Magento\Store\Model\ScopeInterface::SCOPE_STORE, and ~60 for \Magento\Framework\App\Config\ScopeConfigInterface::SCOPE_TYPE_DEFAULT.

[antonkril]

In Magento 2 Scoped config is part of Framework, and stores are part of ECommerce Application. ECommerce Application is built on top of framework, so Framework parts can not know about Application parts.

Magento\Framework\App\Config is Framework level object that does not know about stores (and can not know about current store). So when you ask for config you should specify which scope you want. So it should not be compared to Mage::getStoreConfig.

You can use \Magento\Store\Api\StoreResolverInterface::getCurrentStoreId to get id of currently requested store.

[davidalger]

The GitHub issue tracker is intended for technical issues only. Please refer to the Community Forums or Magento Stack Exchange site for technical questions. In your case, the programming questions forum is likely the most appropriate. Feel free to reopen this issue if you think you have encountered a bug in Magento 2.