Issue Task Resolved

#110745Use dependency injection in DI-ready core classes

Wouter Wolters 09/19/26, 19:09 updated 09/28/26, 19:20

Description

Thirteen container-managed classes across Admin Panel, Backend, Dashboard, Lowlevel, Redirects, and Workspaces still obtain ConnectionPool, Context, or Features through GeneralUtility::makeInstance().

Inject these services through the existing constructors and use the injected properties. Keep the behavior unchanged. Leave objects created outside the DI container untouched.

Reviews 1

History 12

  1. Wouter Wolters commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-28T19:20:10+00:00" > 09/28/26, 19:20 </span>

    Applied in changeset commit:51376babd6a108dc97f5a6391c9fed41102dc5e8.