ProjectInfo should be a service

Created on 28 September 2023, 12 months ago
Updated 2 February 2024, 7 months ago

Problem/Motivation

\Drupal\package_manager\ProjectInfo() is architecturally tortured. It is intended to be a thing that can retrieve useful information about Drupal projects, both installed and not installed...yet it is built as a stateful class that is associated with a single project short name. wat.

Proposed resolution

It should be a service, and you should have to pass in the name of the project you want info for when you call its public methods. Pretty straightforward. This will also pave the path for us to inject more dependencies, including the ones needed to validate that information about available updates matches what we get from composer audit, which is part of how we will tackle 🐛 Rely on TUF-protected resources to determine which updates are available Postponed: needs info .

📌 Task
Status

Needs review

Version

3.0

Component

Package Manager

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024