![]() ![]() Magento\Framework\Config provides the following interfaces: You can use these interfaces if you create a configuration type. You can interact with configuration files using interfaces under Magento\Framework\Config. \Magento\Directory\Model\Country\Postcode\Config\Data \Magento\Framework\App\ResourceConnection\Config\Readerĭefines actions that trigger cache invalidation for private content blocksĭefines options for system configuration page \Magento\Framework\MessageQueue\Topology\Config\Xml\Reader \Magento\WebapiAsync\Code\Generator\Config\RemoteServiceReader\Publisherĭefines the message routing rules, declares queues and exchanges \Magento\Framework\MessageQueue\Consumer\Config\Xml\Readerĭefines the exchange where a topic is published. \Magento\Catalog\Model\ProductTypes\Configĭefines the relationship between an existing queue and its consumer \Magento\Catalog\Model\ProductOptions\Config \Magento\Sales\Model\Order\Pdf\Config\Reader \Magento\Framework\Module\ModuleList\Loader \Magento\Backend\Model\Menu\Config\Readerĭefines module config data and soft dependency \Magento\ImportExport\Model\Import\Config \Magento\Framework\DataObject\Copy\Config\Reader \Magento\Framework\Api\ExtensionAttribute\Config \Magento\ImportExport\Model\Export\Config \Magento\Elasticsearch\Model\Adapter\Index\Config\EsConfig \Magento\Email\Model\Template\Config\Data \Magento\Eav\Model\Entity\Attribute\Config Magento\Framework\Setup\Declaration\Schema \Magento\WebapiAsync\Code\Generator\Config\RemoteServiceReader\Communication These files are readable/writeable by the internal config processor.ĭefines aspects of the message queue system \Magento\Catalog\Model\Attribute\Config\Data \Magento\Framework\Acl\AclResource\Provider ![]() The following table shows each configuration type and the Commerce configuration object to which it relates. The following sections provide information about configuration types, their corresponding configuration objects, and interfaces that you can use to work with the objects: Configuration types and objects Configuration types, objects, and interfaces ![]() You can use \Magento\Framework\Config\Reader\Filesystem class for debugging and understanding the logic behind configuration files loader and merge configs process. is the component’s vendor name for example, Commerce’s vendor name is magento. Typical values are app/code or vendor relative to the Commerce installation directory. is the base directory in which your component is located. Some area-specific configurations can override or extend the global configuration. Collects configuration files from all modules and merges them into the global configuration. Area-specific configuration from modules ( //-/etc//*.xml).Collects certain configuration files from all modules and merges them together. Global configurations from modules ( //-/etc/*.xml).Primary configuration ( app/etc/di.xml).How Commerce loads configuration filesĬommerce loads configuration files in the following order (all paths are relative to your Commerce installation directory): This section discusses how configuration files are loaded and merged. For more information, see Modules and areas. For example, adminhtml is an area scope that is loaded with at the stage with other modules’ adminhtml configurations. For example, module.xml files are merged with other module.xml files.Ĭonfiguration scope-Complementary to configuration stages, a scope defines the configuration type model. Each stage determines when configuration type is loaded and merged with same-named configuration types. For example, the configuration object for config.xml is Magento\Framework\App\Config.Ĭonfiguration stage-Stages are defined as primary, global, and area. Multiple modules can declare configuration files that affect the same configuration type (for example, events), and these multiple configuration files are merged.įollowing are common terms used in this topic:Ĭonfiguration object-The Commerce library or class that is responsible for defining and validating the configuration type. ![]() You can use these files-also referred to as configuration types-to customize specific aspects of your module’s behavior. Commerce’s multiple configuration files load on demand only when a module requests a specific configuration type. The responsibilities of the config.xml configuration file used in earlier versions of Commerce is now divided between several files, located in various module directories. ![]()
0 Comments
Leave a Reply. |