Very curious what is meant by 'before, after, or "around"' ?
around is sort of before and after. A simple example might be some sort of measurement of how long a process takes. You could wrap the measurement action "around" the saving action.
Ah, so the same pattern as with dates - you often want to be able to specify a period of time, with a beginning and an ending.
hmm, don't think that's related. this is about api.
I think the original name for this (Event) was better. Imo here are just four actions: create, read, update, and delete. (We might make a case for "save" as also being an action that means create or update). But there are tons and tons of events (saving subcards, calling flexmail, etc). And, in fact, in the api, I think it makes most sense to be able to specify both, eg "after saving subcards (event) when creating (action)".
'commit' is what is now called 'store' in the code, right?
These are developer issues/use cases, Wagneers won't see this kind of thing. For developers, it may be useful to lay out what the actual 'core' events are that will be 'within' the commit (store) event. In principle, developers can hook onto any of these 'sub-events' with the same keywords, but I think they are probably outside the 'approved' developer APIs. At that level, some small number of exposed events (as listed in the solution) are the official interface, and the other events are completely inside these.
We also need to spec how/which of the main events can interrupt the flow of events to a success. We are mainly throwing exceptions? Some way to return a 'failure' indication? For sure we can add errors to the card object for detail on what failed.
yes, I need to update this ticket to address the issues that you mentioned. Will do today.
Before closing this we need to document current capabilities and ticket remaining todos.
Will be adding more tickets for other todos, but I'm less concerned now that they'll be lost. closing.