Introduce core token support in PluginBase class

+++ b/lib/Drupal/views/Plugin/views/PluginBase.phpundefined
@@ -227,4 +227,85 @@ abstract class PluginBase extends ComponentPluginBase {
+   * Returns a string with any core tokens replaced.
+   * @param string $string

Add a newline

+++ b/lib/Drupal/views/Plugin/views/PluginBase.phpundefined
@@ -227,4 +227,85 @@ abstract class PluginBase extends ComponentPluginBase {
+  /**
+   * Helper method to add available core tokens to a form.

In an oop world helper methods are private. If they must be public they are not "helper functions". And than we shouldn't start this sentence with "Helper function" but with a 3th person verb just like we do in other places :)

Just adding a tag.

I attached new patch with reroll.

Before and after is pretty much the same, as expected.

+++ b/core/modules/views/lib/Drupal/views/Tests/Handler/AreaTest.phpundefined
+++ b/core/modules/views/lib/Drupal/views/Tests/Handler/AreaTest.phpundefined
@@ -79,6 +79,27 @@ public function testUI() {

@@ -79,6 +79,27 @@ public function testUI() {
+    $view = views_get_view('test_example_area');
+    $view->initHandlers();
+
+    // Test the list of available tokens.
+    $available = $view->empty['test_example']->getAvailableGlobalTokens();
+
+    foreach (array('site', 'view') as $type) {
+      $this->assertTrue(!empty($available[$type]) && is_array($available[$type]));
+      // Test that each item exists in the list.
+      foreach ($available[$type] as $token => $info) {
+        $this->assertText("[$type:$token]");

Couldn't we split this up in an extra method (testRenderArea maybe?) and move the UI tests into an extra file, but this is a followup.

I agree that my comment in #17 is more a topic for a follow up.

Can we file the followup now? :)

#1851166: Split Views Area functionality and UI tests

Seems like a nice little improvement.

Committed and pushed to 8.x. Thanks!