Use a data_type key in ContextDefinition and make them extensible

Created on 3 October 2014, almost 11 years ago

Updated 10 May 2025, about 2 months ago

Problem/Motivation

When using the @ContextDefinition annotation for condition or action plugins then the data type (the most important information about the context) is not visible enough. The annotation uses a mix of a simple string and then key value pairs which is inconsistent

Proposed resolution

Introduce a "data_type" key to make the data type visible and consistent.

Remaining tasks

Patch.

User interface changes

none.

API changes

hopefully none, if this can be implemented in a backwards compatible way.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇦🇹Austria klausi 🇦🇹 Vienna

Live updates comments and jobs are added and updated live.

Contributed project blocker
It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.

d8rules

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 2 months ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024