function SettingsTest::testRealDeprecatedSettings

Same name and namespace in other branches
  1. 9 core/tests/Drupal/Tests/Core/Site/SettingsTest.php \Drupal\Tests\Core\Site\SettingsTest::testRealDeprecatedSettings()
  2. 10 core/tests/Drupal/Tests/Core/Site/SettingsTest.php \Drupal\Tests\Core\Site\SettingsTest::testRealDeprecatedSettings()

Tests deprecation messages for real deprecated settings.

@dataProvider providerTestRealDeprecatedSettings @group legacy

Parameters

string $legacy_setting: The legacy name of the setting to test.

string $expected_deprecation: The expected deprecation message.

File

core/tests/Drupal/Tests/Core/Site/SettingsTest.php, line 290

Class

SettingsTest
@coversDefaultClass <a href="/api/drupal/core%21lib%21Drupal%21Core%21Site%21Settings.php/class/Settings/11.x" title="Read only settings that are initialized with the class." class="local">\Drupal\Core\Site\Settings</a> @runTestsInSeparateProcesses @group Site

Namespace

Drupal\Tests\Core\Site

Code

public function testRealDeprecatedSettings(string $legacy_setting, string $expected_deprecation) : void {
    $settings_file_content = "<?php\n\$settings['{$legacy_setting}'] = 'foo';\n";
    $class_loader = NULL;
    $vfs_root = vfsStream::setup('root');
    $sites_directory = vfsStream::newDirectory('sites')->at($vfs_root);
    vfsStream::newFile('settings.php')->at($sites_directory)
        ->setContent($settings_file_content);
    $this->expectDeprecation($expected_deprecation);
    // Presence of the old name in settings.php is enough to trigger messages.
    Settings::initialize(vfsStream::url('root'), 'sites', $class_loader);
}

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.