Convert _access_tracker_own_information to a one-off access checker

Can't we rename that to: _access_own_user or something like that and make it usuable in other places?

At least for views I would love to have exactly that functionality on an access plugin.

I believe this issue is outdated since the ViewOwnTrackerAccessCheck class no longer exists. Feel free to re-open if I am incorrect.

Re-rolled patch.

+++ b/core/modules/tracker/src/Controller/TrackerUserRecent.php
@@ -18,4 +19,14 @@ public function getContent(UserInterface $user) {
+    $account = \Drupal::currentUser();

You could probably use $this->currentUser()

+++ b/core/modules/tracker/src/Controller/TrackerUserRecent.php
@@ -18,4 +20,26 @@ public function getContent(UserInterface $user) {
+    if ($user && $account->isAuthenticated() && $user->id() == $account->id()) {
+      $result = AccessResult::allowed();
+    }
+    else {
+      $result = AccessResult::neutral();
+    }

What about using $result = AccessResult::allowedIf($user && ...); return $result->cachePermissions() ...

Sorry for another round of annoying questions.

1. +++ b/core/modules/tracker/src/Controller/TrackerUserRecent.php
   @@ -18,4 +20,21 @@ public function getContent(UserInterface $user) {
   +    return AccessResult::allowedIf($user && $account->isAuthenticated() && $user->id() == $account->id())
   

   One question: how could $user be false, even if it is passed in as argument? Wouldn't the access resolver stop if the user wasn't passed in, in the first place?

2. +++ b/core/modules/tracker/src/Controller/TrackerUserRecent.php
   @@ -18,4 +20,21 @@ public function getContent(UserInterface $user) {
   +      ->cachePerPermissions()
   

   Do you know the reason why cachdPermissions() was there? At least for me its not obvious why this condition varies by permissions of users.

1) It's probably left over from the conversion from $GLOBALS['user']

Do you think we can clean this up?

2) I'm assuming it was to address the ->isAuthenticated() check. I guess ->cachePerUser() is enough?

Yeah, the cachePerUser is sort of a superset of cache by permission.

Addressed issues identified in #13/#14/#15.

Thank you @markdorison

Committed/pushed to 8.3.x, thanks!