Option to ignore unknown events

[fritz-gerneth]

On my dev env, I sometimes have events in the store that are not mapped on the current branch (e.g. switching feature branches / ... ). Right now I have to clean up the store everytime is switch.

What do you think of an option to just log this as a warning instead of throwing an exception?

My take: provide an Upcaster that converts unknown events into a Dummy UnknownEvent class and logs a warning. Then the symfony bundle could conditionally register it based on a flag

[DanielBadura]

I don't think this is a good idea, as this will lead to undefined state's in dev and maybe even bugs in production due to missing events which where ignored before. IMHO unlike headers (#818) events should not be missing.

In my projects I often have a script/target which initializes the project into a dev-ready state, including preparing the database, e.g. make init. This is what I'm using to switch branches even if I added new events in another branch I can quickly switch between them but with the cost of resetting the database.

Couldn't you already achieve something like this with an custom upcaster using the event registry?

@DavidBadura wdyt?

[fritz-gerneth]

In my projects I often have a script/target which initializes the project into a dev-ready state, including preparing the database, e.g. make init.

Ours is too large for this :( But we'll get there eventually.

At the moment I am using an custom upcaster, works fine for us. I agree it is a somewhat dangerous setting which certainly should not be enabled by default.