Parse more information out of deprecation messages

Created on 14 February 2019, about 6 years ago
Updated 4 July 2024, 9 months ago

Problem/Motivation

On #3024341: Improve deprecation listing with filtering , we updated the Deprecations page.

But what would be really good would be to have more fields we could filter on, such as:
- What version was the item first deprecated in
- When will it be removed

To do this, we would need to parse either the @deprecated documentation, or the messages in calls to trigger_error and extract these two pieces of information.

To do that, we would have to have a consistent format for deprecation messages. This is currently being worked on in the Coding Standards project on issue
#3024461: Adopt consistent deprecation format for core and contrib deprecation messages

Proposed resolution

a) Once the standard format is adopted, figure out how to parse the messages and save the information in the API module database.
b) Update the Deprecated page to display/filter on this information.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

2.0

Component

Parser

Created by

🇺🇸United States jhodgdon Spokane, WA, USA

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024