The initiating user field that was added with #188 has to be implemented and specified in all commands and events* thus makes it quite tedious and error prone to work with
The recorded_at timestamp of the RawEvent is currently the only option to determine the last updated time of a node. But it is change whenever a content stream is rebased
Suggestion:
Move initiatingUserIdentifier to the event metadata and add another metadata for the timestamp (e.g. initiatingTimestamp) and add those when publishing new events (and copy them when rebasing).
Implementation
Maybe we can extend the command handlers such that they can be created in a certain context, e.g.:
Two problems:
initiating user
field that was added with #188 has to be implemented and specified in all commands and events* thus makes it quite tedious and error prone to work withrecorded_at
timestamp of theRawEvent
is currently the only option to determine the last updated time of a node. But it is change whenever a content stream is rebasedSuggestion:
Move
initiatingUserIdentifier
to the event metadata and add another metadata for the timestamp (e.g.initiatingTimestamp
) and add those when publishing new events (and copy them when rebasing).Implementation
Maybe we can extend the command handlers such that they can be created in a certain context, e.g.:
and in the command handler s.th. along the lines of:
* We forgot to implement it in
NodeAggregateTypeWasChanged