Add machine name to each module's name for easier identification

Great idea. Patch is simple Form API code, clearly appropriate, and works well. Make it so.

P.S.: Here's the screenshot:

This would be helpful for me but I'd also *really* like a link to the project page. If you click on the project name, it gives you the upgrade status details. I'm wondering if this new column should be combined with a link off to the project page to handle this case as well. Thoughts?

There is an abudance of columns and you already need a sizable screen to fit it all :D So I am a bit wary to add more. If we can come up with creative ways to present this differently or some existing data differently so that it fits better that would be great.

True :) What about tacking it onto the end of the first column, e.g. MEDIA ENTITY DOCUMENT (media_entity_document)?

Hello, adding a patch with the suggestion from #11 and a screenshot.

I haven't updated the title and IS to wait to see if this approach is accepted first.
If you want i can change the MR as well.

Thanks for updating the patch. A couple things:

1. +++ b/src/Form/UpgradeStatusForm.php
   @@ -340,6 +340,8 @@ class UpgradeStatusForm extends FormBase {
   +      $extension_pathname = $extension->getPathname();
   +      $extension_machine_name = explode('.', basename($extension_pathname))[0];
   

   Nitpick: How about combining these into one line? e.g.

   $extension_machine_name = explode('.', basename($extension->getPathname()))[0];
   

2. +++ b/src/Form/UpgradeStatusForm.php
   @@ -348,7 +350,7 @@ class UpgradeStatusForm extends FormBase {
   -            '#value' => $extension->info['name'],
   +            '#value' => $extension->info['name'] . " (" . $extension_machine_name . ")",
   

   Nitpick: To be consistent with other code, it would be good to change the double quotes to single quotes like shown here:

   '#markup' => ' (' . $last_checked . ')',
   

I think it looks good :)

Actually, I see there is a $extension->getName() that could be used instead of getting the name yourself, so how about just using:

'#value' => $extension->info['name'] . ' (' . $extension->getName() . ')',

or, alternatively, adding the $extension->getName() when $extension->info['name'] gets set instead.

Changing the patch to get the $extension->getName() instead of $extension->getPathname() as suggested in #17.

Looks cleaner now :)

Thanks! Re linking to the project page @kristen_pol, the drupal.org issues column already links to a filtered issue queue for the project. The project page itself should be one click from there. I know that is not a direct link but there is only so much space in this table :D

Fix race condition problem :D