ConfigurationManager.php

Go to the documentation of this file.

<?php
 
declare(strict_types=1);
 
/*
 * This file is part of the TYPO3 CMS project.
 *
 * It is free software; you can redistribute it and/or modify it under
 * the terms of the GNU General Public License, either version 2
 * of the License, or any later version.
 *
 * For the full copyright and license information, please read the
 * LICENSE.txt file that was distributed with this source code.
 *
 * The TYPO3 project - inspiring people to share!
 */
 
namespace ‪TYPO3\CMS\Extbase\Configuration;
 
use Psr\Container\ContainerInterface;
use Psr\Http\Message\ServerRequestInterface;
use ‪TYPO3\CMS\Core\Http\ApplicationType;
use ‪TYPO3\CMS\Extbase\Configuration\Exception\InvalidConfigurationTypeException;
 
class ‪ConfigurationManager implements ‪ConfigurationManagerInterface
{
    private ContainerInterface ‪$container;
 
    protected ‪FrontendConfigurationManager|‪BackendConfigurationManager ‪$concreteConfigurationManager;
 
    private ?ServerRequestInterface ‪$request = null;
 
    public function ‪__construct(ContainerInterface ‪$container)
    {
        $this->container = ‪$container;
        $this->‪initializeConcreteConfigurationManager();
    }
 
    protected function ‪initializeConcreteConfigurationManager(): void
    {
        // @todo: Move into getConfiguration() in v13.
        //        This will allow getting rid of $GLOBALS['TYPO3_REQUEST'] here, and the
        //        concrete ConfigurationManager is created "late" in getConfiguration().
        //        Check $this->concreteConfigurationManager for null. If null, fetch request from
        //        $this->request() (and *maybe* check TYPO3_REQUEST as b/w layer, better not), if still
        //        null, fall back to BackendConfigurationManager.
        //        Background: People tend to inject ConfigurationManager into non-extbase bootstrapped
        //        classes since the getConfiguration() API is so convenient. If request has not been set
        //        via setRequest(), this *may* indicate a CLI call. Extbase in general needs requests for
        //        controllers, but we *may* want to allow getting ConfigurationManager injected as
        //        "standalone" feature in CLI as well? OTOH, we could avoid this, when the TypoScript
        //        factories have been refactored far enough to be easily usable. If so, the request
        //        properties should be made non-nullable.
        if ((‪$GLOBALS['TYPO3_REQUEST'] ?? null) instanceof ServerRequestInterface
            && ‪ApplicationType::fromRequest(‪$GLOBALS['TYPO3_REQUEST'])->isFrontend()
        ) {
            $this->concreteConfigurationManager = $this->container->get(FrontendConfigurationManager::class);
        } else {
            $this->concreteConfigurationManager = $this->container->get(BackendConfigurationManager::class);
        }
    }
 
    public function ‪setRequest(ServerRequestInterface ‪$request): void
    {
        $this->request = ‪$request;
        // @todo: Move to getConfiguration() together with "late" creation of $this->concreteConfigurationManager
        $this->concreteConfigurationManager->setRequest($this->request);
    }
 
    public function ‪setConfiguration(array $configuration = []): void
    {
        // @todo: If really needed in v13 and if it can't be refactored out, park
        //        state in a property and $this->concreteConfigurationManager->setConfiguration()
        //        after concreteConfigurationManager has been created in getConfiguration().
        $this->concreteConfigurationManager->setConfiguration($configuration);
    }
 
    public function ‪getConfiguration(string $configurationType, string $extensionName = null, string $pluginName = null): array
    {
        switch ($configurationType) {
            case ‪self::CONFIGURATION_TYPE_SETTINGS:
                $configuration = $this->concreteConfigurationManager->getConfiguration($extensionName, $pluginName);
                return $configuration['settings'] ?? [];
            case ‪self::CONFIGURATION_TYPE_FRAMEWORK:
                return $this->concreteConfigurationManager->getConfiguration($extensionName, $pluginName);
            case ‪self::CONFIGURATION_TYPE_FULL_TYPOSCRIPT:
                return $this->concreteConfigurationManager->getTypoScriptSetup();
            default:
                throw new ‪InvalidConfigurationTypeException('Invalid configuration type "' . $configurationType . '"', 1206031879);
        }
    }
}