search

TurtleAI / derive

An Event Sourcing and CQRS solution.
0 stars 1 forks source link

Events produced by services aren't populated `source_event_id` #26

Closed rwillians closed 1 year ago

rwillians commented 1 year ago

Example of an event that was produced by a service and didn't get it's :source_event_id populated.

{
    "id": "30870348649259176310057341550594",
    "time": "2022-10-18T15:00:00.578187Z",
    "__type__": "Elixir.Hatch.TimeTracker.Events.TimeEntriesInvoiced",
    "command_id": null,
    "invoice_id": "30870348649203836077836212895744",
    "request_id": null,
    "time_entry_ids": [
        "30870348648779560964140893208576"
    ],
    "source_event_id": null
}

@venkatd do we need some sort of custom commit callback for our services?

venkatd commented 1 year ago

@rwillians I've updated the Turtle.EventStore.commit implementation to add this in and pushed a commit to dev. Had to expose an api on the Derive side. Please confirm if it is working as expected.