How to store Subslot/EventView information in EventContext
The following discussion from !732 (merged) should be addressed:
-
@ishapova started a discussion: (+5 comments) In line with what I said in the other comment, an event context cannot be a sub-slot, it can be an event view context.
I've added a member (with get and set methods) to the EventContext to store an index for a sub-slot entry for an EventView w.r.t. the parent "event level" slot. However, there's some room for improvement in the naming and exact information stored.
We should improve/eliminate this in the long term, especially since the information really isn't useful outside the scheduler, and ideally we should prevent it from being used.