>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3501643. --> Reported by: [bramdriesen](https://www.drupal.org/user/3383264) Related to !19 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>This has been a discussion point in the MR's of our team for our projects. Mainly about functions calls like <code>\Drupal::</code> in none name-spaced files (e.g. .module, .install, .api,...).</p> <p>I would usually write my code with the leading backslash.</p> <div class="codeblock"> <pre><span style="color: #000000"><span style="color: #0000BB">&lt;?php<br>$facet_manager </span><span style="color: #007700">= \</span><span style="color: #0000BB">Drupal</span><span style="color: #007700">::</span><span style="color: #0000BB">service</span><span style="color: #007700">(</span><span style="color: #DD0000">'facets.manager'</span><span style="color: #007700">);<br></span><span style="color: #0000BB">?&gt;</span></span></pre></div> <p>But then a team member would come in saying the leading backslash is not required as we're not in a namespace. Looking at Drupal core, I can see a mix of both being used, so I think it's good if we could standardise this as a standard.</p> <p>Core example where it is done with a <code>\</code> : <a href="https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/automated_cron/automated_cron.module?ref_type=heads#L13">https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/automated_cron/automated_cron.module?ref_type=heads#L13</a></p> <p>Core example where it is done withouth a <code>\</code> : <a href="https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/toolbar/toolbar.module?ref_type=heads#L41">https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/toolbar/toolbar.module?ref_type=heads#L41</a></p> <p>Happy to say thought that there are not that many cases without the <code>\</code> in Drupal Core. I did a code search today on the 11.x branch in PHPStorm (since it's not possible to search on Drupal:: with GitLab code search) and only found 2 code occurrences. Screenshot attached.</p> <h3 id="summary-benefits">Benefits</h3> <p>By enforcing this change, function calls like <code>\Drupal::</code> are written the same everywhere when not in a namespace.</p> <h3 id="summary-supporters">Three supporters required</h3> <ol> <li><a href="https://www.drupal.org/u/borisson_">https://www.drupal.org/u/borisson_</a> (2025-01-23)</li> <li><a href="https://www.drupal.org/u/drunken-monkey">https://www.drupal.org/u/drunken-monkey</a> (2025-01-23)</li> <li><a href="https://www.drupal.org/u/sophie.sk">https://www.drupal.org/u/sophie.sk</a> (2025-02-21)</li> <li><a href="https://www.drupal.org/u/Kingdutch">https://www.drupal.org/u/Kingdutch</a> (2026-04-28)</li> </ol> <h3 id="summary-proposed-changes">Proposed changes</h3> <p>Provide all proposed changes to the Drupal <a href="https://www.drupal.org/docs/develop/standards">Coding standards</a>. Give a link to each section that will be changed, and show the current text and proposed text as in the following layout:</p> <h4>1. <a href="https://www.drupal.org/docs/develop/coding-standards/namespaces#s-use-ing-classes">Namespaces &raquo; Using classes</a></h4> <h5>Current text</h5> <blockquote><p> Classes and interfaces without a backslash <code>\</code> inside their fully-qualified name (for example, the built-in PHP Exception class) must be fully qualified when used in a namespaced file. For example: <code>new \Exception();</code>. Do not <code>use</code> global classes. </p></blockquote> <h5>Proposed text</h5> <blockquote><p> Classes and interfaces without a backslash <code>\</code> inside their fully-qualified name (for example, the built-in PHP <code>Exception</code> class) must be fully qualified. For example: <code>new \Exception();</code>. Do not <code>use</code> global classes. </p></blockquote> <h4>2. Repeat the above for each page or sub-page that needs to be changed.</h4> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li><del>Create this issue in the Coding Standards queue, using the defined template</del></li> <li><del>Add supporters</del></li> <li><del>Create a Change Record</del></li> <li><del>Review by the Coding Standards Committee</del></li> <li>Coding Standards Committee takes action as required</li> <li>Discussed by the Core Committer Committee, if it impacts Drupal Core</li> <li>Final review by Coding Standards Committee</li> <li>Documentation updates <ol> <li>Edit all pages</li> <li>Publish change record</li> <li>Remove 'Needs documentation edits' tag</li> </ol> </li> <li>If applicable, create follow-up issues for PHPCS rules/sniffs changes</li> </ol> <p>For a full explanation of these steps see the <a href="https://www.drupal.org/project/coding_standards" title="Coding Standards project page">Coding Standards project page</a></p>