Skip to content

Suggested Improvement: Modify the Implementation of eventTrigger to Use a List #605

Open
@garfcat

Description

Suggested Improvement: Modify the Implementation of eventTrigger to Use a List

I would like to propose a change in the implementation of eventTrigger from a map to a list. This modification would allow for the execution of different functions for the same event. Currently, the implementation uses a map, which makes it impossible to perform different actions on the same event. For example, when dealing with the shadowCreateOrUpdateTrigger event, there might be a need to update a cache and also send a message to a message queue. With the current implementation, it would require registering two separate events to achieve this functionality.

By transitioning to a list-based approach, it becomes feasible to execute multiple actions for a single event, providing greater flexibility and efficiency in handling event-triggered tasks.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions