What was the reason behind the "Event" naming? Alternative naming suggestions

[alex-stoica]

I noticed that a workflow Event is implemented as a subclass of BaseModel, mimicking a dictionary interface. However, based on its functionality and usage, the name "Event" seems a bit unintuitive as it doesn't necessarily behave like what one would typically associate with in other contexts (e.g., an action trigger). Instead, it seems to serve more as a structured state or snapshot of some process. Given that, I was wondering whether you'd consider something like State, Phase, Waypoint or even Slate be more intuitive? Maybe I am missing something in how an Event is intended to be used.

[masci]

Workflows evolved a bit from the first draft, but I still see them as an event-driven system. The Reason why they implement BaseModel is to ease the way you can define and attach a payload to each event. How do you see an action trigger different?

[alex-stoica]

I think it was more of a confusion from my side, as llamaindex events can really act as triggers (+ attached payloads). I think I'm more used to events that are lightweight triggers, wo data / with little data attached. What I've suggested captures the data-holding aspect, but not the triggering nature. Thanks for the clarification!