@rodrigo.pedra This may sound strange, but following the docs I had no good result, so I had to look into the source code and find out that the docs were "lying", my Reactor was expecting a StoredEvent object according to the docs, but the library was actually emitting my own event back with an additional metaData property.
So I was using an Aggregator, when you persist the event, basically, save it in database using's the AggreagatorRoot's method "persist" according to the docs, if I add to the method that I am using in my Reactor which is tied to my custom event, as a parameter, the StoredEvent, to have access to the stored event that was saved, I should have access to the stored event but it's not really true. The library is firing back my own custom event with the additional metaData that I needed.
The docs: "Persisting an aggregate root will write all newly recorded events to the database. The newly persisted events will get passed to all projectors and reactors."
Then it goes on showing an example with the "StoredEvent" being passed to a projector, but this was not the event that was being emitted, it was actually my custom event that. I said that maybe it's not working for the Reactor and tried a Projector, same thing, that "StoredEvent" was not there, the only event emitted was my custom even with additional metaData. I tried the example code and was not working.
And I had this config dispatch_events_from_aggregate_roots to true.