Consider a mechanic for "callbacks"

Created on 20 May 2022, about 3 years ago
Updated 13 July 2023, about 2 years ago

Problem/Motivation

We have a mechanic for building reusable components using custom events (and entity-aware custom events when eca_content is enabled). This mechanic brings in two possible problems:

  1. There is no dependency being defined between the calling configuration (the one that triggers the custom event) and the one that reacts upon that event. This missing definition introduces the risk of losing components without being notified about that.
  2. Usability may be counter-intuitive, as the matching between the affected events are defined by the custom defined event ID. It's event harder to understand how Token forwarding works.

Have not marked this one for stable release 1.0 as this issue is somewhat abstract and not a concrete use case. It's just an idea that came up while building ECA VBO where ECA configurations are being exposed as bulk operations.

Steps to reproduce

Proposed resolution

We could provide a mechanic to expose ECA configurations as "callbacks", and offer an action that allows to select available callbacks from a dropdown.

The term "callback" includes "back" which means this mechanic should also provide an intuitive way how to get a return result.

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

1.2

Component

Miscellaneous

Created by

🇩🇪Germany mxh Offenburg

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