deprecate drupal_requirements_url() and move to a method on RequirementSeverity enum

Created on 23 May 2025, 11 days ago

Problem/Motivation

Follow up to πŸ“Œ Create enums for RequirementSeverity and RequirementPhase Active Now we have RequirementSeverity we can move the logic of drupal_requirements_url() there and deprecate it.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component

extension system

Created by

πŸ‡¦πŸ‡ΊAustralia kim.pepper πŸ„β€β™‚οΈπŸ‡¦πŸ‡ΊSydney, Australia

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

Comments & Activities

  • Issue created by @kim.pepper
  • πŸ‡¦πŸ‡ΊAustralia kim.pepper πŸ„β€β™‚οΈπŸ‡¦πŸ‡ΊSydney, Australia

    Looks like drupal_requirements_url() is the only caller of drupal_current_script_url() so both of these can be deprecated. I don't think putting them on the RequirementSeverity enum is the right place. These functions are used by the install script to pass query params around.

  • πŸ‡ΊπŸ‡ΈUnited States nicxvan

    Yeah I don't think they belong on the enum.

    I do think it belongs in the same namespace though.

    What about Url or Check?

    If it's Url we would move just these two probably.

    If we call it Check or Checker we could move most of the things remaining in install.inc

  • πŸ‡ΊπŸ‡ΈUnited States nicxvan
Production build 0.71.5 2024