How are the «generated/medatata» files used in Magento 2.2?

Development Compilation

dmitry_fedyuk (Dmitrii Fediuk) October 13, 2017, 1:01pm 1

1. Magento\Framework\App\Filesystem\DirectoryList::GENERATED_METADATA

github.com

magento/magento2/blob/2.2.0/lib/internal/Magento/Framework/App/Filesystem/DirectoryList.php#L133-L136


/**
 * Relative directory key for generated metadata
 */
const GENERATED_METADATA = 'metadata';

2. Magento\Framework\App\ObjectManager\ConfigLoader\Compiled::getFilePath()

github.com

magento/magento2/blob/2.2.0/lib/internal/Magento/Framework/App/ObjectManager/ConfigLoader/Compiled.php#L36-L46


/**
 * Returns path to compiled configuration
 *
 * @param string $area
 * @return string
 */
public static function getFilePath($area)
{
    $diPath = DirectoryList::getDefaultConfig()[DirectoryList::GENERATED_METADATA][DirectoryList::PATH];
    return BP . '/' . $diPath . '/' . $area . '.php';
}

How are the «generated/medatata» files generated in Magento 2.2?

How are the interceptors generated on «setup:di:compile» in Magento 2.2?

dmitry_fedyuk (Dmitrii Fediuk) October 13, 2017, 1:01pm 2

See also: