You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
- applications don't need to call onEvent in a persist handler anymore
- closes#93
Further changes:
- command handler can now be defined as override def onCommand = ...
- event handler can now be defined as override def onEvent = ...
- snapshot handler can now be defined as override def onSnapshot = ...
- applications don't need to call onEvent in a persist handler anymore
- closes#93
Further changes:
- command handler can now be defined as override def onCommand = ...
- event handler can now be defined as override def onEvent = ...
- snapshot handler can now be defined as override def onSnapshot = ...
At the moment, a
persist
handler must explicitly callonEvent
for successfully persisted events:This should be automated so that application code doesn't need to call
onEvent
anymore:The text was updated successfully, but these errors were encountered: