Show more context in config source overview

I'm not sure how much we really want to customize per config type here.

What we could do is add the config ID somehow, e.g. smaller behind the label?

The bundle filters etc. that we have for node are generic, there is no way to figure out in a generic way that fields can be filtered by entity type/bundle.

It looks like that most of the config types are linkable. It is also possible for fields to be linkable as well - so I am adding support with this patch. It was a bit tricky but it should be better ux now.

For config types that don't have edit form link template/route I am adding {label} ({configuration_id}).

Added a new (configuration id) column and tests. Here is how it looks like:

Fixed "Configuration ID" and added tests for one more case - fields without field-edit-form link template.

As now, from 4 cases possible: config entities with edit form link template, fields with specific field-edit-form link template, config entities without edit-form link template - we have no tests for fields with specific field-edit-form link template but with a wrong route...
I bumped into this case (Exception) when I enabled CRM Core module. I am pretty sure this won't happen when we fix CRM Core link templates/routes...

But throwing an uncaught exception is simply wrong. The UI needs to catch it and handle it gracefully. Even if the situation is unclean.

Yes, that's why we handled this exception since #6

Debugged a bit, but not sure what is the exact problem nor solution. Tried to explain a problem more in: https://github.com/md-systems/crm_core/issues/37

+++ b/sources/tmgmt_config/src/ConfigSourcePluginUi.php
@@ -124,13 +127,34 @@ class ConfigSourcePluginUi extends SourcePluginUiBase {
+    // Do the special link handling for fields.
+    elseif ($entity instanceof FieldConfigInterface) {
+      $edit_field_form_link_template = $entity->getTargetEntityTypeId() . '-field-edit-form';
+      if ($entity->hasLinkTemplate($edit_field_form_link_template)) {
+        $link = $entity->toLink($label, $edit_field_form_link_template);
+        try {
+          if (!empty($link->getUrl()->toString())) {
+            $row['title'] = $link;
+          }
+        }

I'm not convinced this special case is worth it.

As you've found yourself, it can case problems. I think CRM is caused by CRM not having a field ui base route, or maybe that's part of a UI module that's not enabled/ported yet, not sure.

What exactly does a user gain by being able to go there? If special case anything, I'd rather build a combined label that includes the entity type and bundle for this. But as discussed above, I'd rather avoid hardcoding things.

What exactly does a user gain by being able to go there?

I guess it's the same benefit as for others config entities - more info about the source.

I think CRM is caused by CRM not having a field ui base route

Most likely.

Okay, removed the special case for fields. The patch looks clean now. :)

Ok, committed this.

Found #2689795: Check for continuous jobs must not be shown for config entities while testing this.