>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3629468. --> Reported by: [nwoodland](https://www.drupal.org/user/2819229) >>> <h3>Problem/Motivation</h3> <p>This is one concrete slice of the work in the roadmap (<a href="https://www.drupal.org/project/entity_usage_root/issues/3626846">#3626846</a>) that we propose for 1.0.0-alpha3. It targets stability and clear UX improvements, and does not change relationship storage.</p> <p>Current status on 1.0.x (alpha2): the full test suite (28 Kernel and 5 Functional tests) passes on Drupal 11.4 with PHP 8.3, and phpcs is clean. We have not yet run it on Drupal 10. There is no <code>.gitlab-ci.yml</code>, so the tests do not run on drupal.org.</p> <h3>Proposed resolution</h3> <ol> <li><strong>Drupal.org CI.</strong> Add <code>.gitlab-ci.yml</code> using the shared GitLab Templates (phpcs, phpstan, cspell, eslint, PHPUnit), and a <code>composer.json</code>. Test against the previous minor, next minor and next major core versions, to match our <code>^10.3 || ^11</code> support.</li> <li><strong>Length-safe identifiers</strong> (roadmap item 1). Make the generated base field, table, View, route and local-task identifiers safe against length limits and collisions. Add an update hook for existing installs that leaves customised Views alone.</li> <li><strong>Generated report labels</strong> (roadmap item 3). <ul> <li>Local task: change "@leaf on @root" to "@root usage" (for example "Content usage"). It appears inside the leaf's own section.</li> <li>View label and page title: change to "@leaf: @root usage" (for example "Media: Paragraph usage"), so they stay unambiguous in the Views admin list, breadcrumb and page title.</li> <li>Column labels: "Thumbnail" becomes "Media thumbnail" when the leaf is Media. "Edit @entity" becomes "@entity operations".</li> <li>Paths stay unchanged.</li> <li>The update hook regenerates only Views that have not been customised.</li> </ul> </li> <li><strong>Batch update prerequisites</strong> (roadmap item 2). Before the batch starts, check that tracking is enabled for each configured type, that the tracking config is not empty, and that the <code>entity_usage</code> table has data. Show the results as warnings on the form, and disable the button only when nothing can be rebuilt. Share one check across the rebuild form, the settings form and the Drush command. Open question: should the tab, route and action also be renamed to "Batch update" to match Entity Usage?</li> <li><strong>Internal cleanup</strong> (part of roadmap item 4). Move the <code>cron</code> and <code>views_data_alter</code> hooks out of <code>EntityUsageRootEntityHooks</code> into focused hook classes. Add an interface for the View builder service and rename it to <code>EntityUsageRootViewsBuilder</code>, keeping a service alias for one release. No behaviour change is intended.</li> </ol> <h3>Remaining tasks</h3> <ul> <li>Run the baseline on Drupal 10 and fix anything found.</li> <li>Fix deprecations in our own code and tests (<code>getDrupalRoot()</code>, <code>#[LegacyRequirementsHook]</code>, <code>#[RunTestsInSeparateProcesses]</code>).</li> <li>Add the CI files and fix what the first pipeline run exposes.</li> <li>Implement items 2 to 5 above.</li> <li>Add tests that guard against regressions: <ul> <li>Exact assertions for the tab, View label, title and column strings, for Media and non-Media leaves with several roots each.</li> <li>Identifier names at and over the limits, a collision case, and stability across repeated syncs.</li> <li>The update hook regenerates an untouched alpha View, leaves a customised one alone, and is idempotent.</li> <li>A Functional test for each missing batch prerequisite.</li> <li>For the refactor, the existing tests pass unchanged, plus a test for the service alias.</li> </ul> </li> <li>Update the README for the new labels, the batch prerequisites and CI.</li> </ul> <h3>Not in this slice</h3> <p>The optional <code>entity_usage_root_views</code> submodule, the decision on the standalone overview page, the beta test matrix (permissions, revisions, large rebuilds), and the deferred items in the roadmap. Features such as export or search over the generated reports would need their own issues.</p> <h3>User interface changes</h3> <p>Local task text, generated View labels and titles, and two column labels change as described above. Batch update gains prerequisite warnings.</p> <h3>API changes</h3> <p>A new interface for the View builder service. The service is renamed to <code>EntityUsageRootViewsBuilder</code>, and the old service id remains as an alias for one release.</p> <h3>Data model changes</h3> <p>No change to relationship storage. Length-safe identifiers may rename generated fields, tables and Views through an update hook, which preserves customised Views.</p>