Core services individual pages not helpful and jumping to the top result in searches

This appears to be related to parsing core.services.yml, which also causes other problems that I discuss in 🐛 Many service names do not show up in 11.x documentation Active

In this case, core.services.yml defines the file_system service like this:

  file_system:
    class: Drupal\Core\File\FileSystem
    arguments: ['@stream_wrapper_manager', '@settings']
  Drupal\Core\File\FileSystemInterface: '@file_system'

So here, "Drupal\Core\File\FileSystemInterface" is actually a STRING alias for the file_system service - that's what's showing up in your search. It's NOT a class name even though it appears to be one.

This syntax in core.services.yml is for Symfony to do autowiring of services - Symfony can now automatically inject the file_system service by recognizing either the FileSystem class name or the FileSystemInterface interface name in the constructor arguments to other services, instead of having to specify @file_system in an arguments list for those other services.

Oh, that explains the weird fully namespaced first choice there, it's the alias that seems to be messing things around. Wondering if we can just ignore aliases in this case, I'm not too familiar with the autowiring from Symfony to know whether it's something relevant that needs to be there, parsed and processed, or if we can just ignore it.

I'm also wondering if the parsing of those aliases is actually making it ignore the service right below them. That could explain 🐛 Many service names do not show up in 11.x documentation Active .

If I enter FileSystemInterface in the Search drupal 11.x search box, I get only a result: the interface itself.

Drupal\Core\File\FileSystemInterface, which would take to the service page, is not shown.

Actually, I cannot even get to a service page when I search for file_system, the service name.

@avpaderno: That's what I reported in 🐛 Many service names do not show up in 11.x documentation Active