>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3464159. --> Reported by: [tr](https://www.drupal.org/user/202830) Related to !55 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>A huge number of services are missing from the 11.x documentation. Here are just some that can't be found (and yes, they are still all part of core 11.x and listed in the <code>core.services.yml</code>, and they all show up in the 10.x, 9.x etc. documentation):</p> <ul> <li>config.factory</li> <li>current_user</li> <li>entity_type.manager</li> <li>event_dispatcher</li> <li>logger.factory</li> <li>module_handler</li> </ul> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>This is what I mean by can't be found:<br> A search on a service name (in the main search box) should bring up results.</p> <p>For example, in the 10.x documentation, search for <code>entity_type.manager</code>:<br> <a href="https://api.drupal.org/api/drupal/core%21core.services.yml/service/entity_type.manager/10">https://api.drupal.org/api/drupal/core%21core.services.yml/service/entity_type.manager/10</a></p> <p>This brings up a page showing the class that provides the service, a link to <code>core.services.yml</code>, and a list of files that use this service.</p> <p>This is helpful.</p> <p>But in the 11.x documentation, a huge number of searches like this yield <strong>no result</strong> at all.</p> <p>For the above search, when you open up the "Same name and namespace in other branches" section you can see that <code>entity_type.manager</code> is not listed as being present in 11.x. That's obviously wrong.</p> <p>Searching directly:<br> <a href="https://api.drupal.org/api/drupal/11.x/search/entity_type.manager">https://api.drupal.org/api/drupal/11.x/search/entity_type.manager</a><br> returns nothing.</p> <p>Likewise, going directly to the services search:<br> <a href="https://api.drupal.org/api/drupal/services/11.x">https://api.drupal.org/api/drupal/services/11.x</a><br> returns nothing for <code>entity_type.manager</code></p> <h3 id="summary-proposed-resolution">Probable cause</h3> <p>Services can now be autowired, and have aliases. <a href="https://www.drupal.org/node/3323122">Core services provide aliases for autowiring</a> My guess is that <code>core.service.yml</code> is not being parsed correctly for this change. However, the change was made back in D10.1 and the 10.x documentation DOES work correctly for these services, so I'm not sure how this fully explains the problem.</p> <p>For example, in D10, <code>core.services.yml</code> looks like this for the current_user service:</p> <pre>&nbsp; current_user:<br>&nbsp;&nbsp;&nbsp; class: Drupal\Core\Session\AccountProxy<br>&nbsp;&nbsp;&nbsp; arguments: ['@event_dispatcher']</pre><p> While in D11 it looks like this:</p> <pre>&nbsp; current_user:<br>&nbsp;&nbsp;&nbsp; class: Drupal\Core\Session\AccountProxy<br>&nbsp;&nbsp;&nbsp; arguments: ['@event_dispatcher']<br>&nbsp; Drupal\Core\Session\AccountInterface: '@current_user'<br>&nbsp; Drupal\Core\Session\AccountProxyInterface: '@current_user'</pre><p> In this case, there are aliases for the purpose of autowiring, so that Symfony can automatically inject the service based on either the class name or one of the two interface names.</p> <p>Searching for <code>current_user</code>, <code>AccountProxy</code>, <code>AccountInterface</code>, or <code>AccountProxyInterface</code> finds <strong>nothing</strong> in the 11.x search of services, but DOES work in the 10.x search. </p>