Question - Best practises regarding CRUD events about laravel-event-sourcing HOT 2 CLOSED

Spatie has a style guide that provides a sensible explanation of why you would name your events in a past-tense: https://guidelines.spatie.be/code-style/laravel-php#naming-classes

These naming decisions are up to you for your project. It's a style decision.

If you're setting hours, an InvoiceUpdated event is fine. In the bank example, you wouldn't want to set that value. You'd want to increment or decrement it. This is so the correct calculation is applied to the existing aggregate vs. calculating based on the currently projected data.

from laravel-event-sourcing.

As for your additional question, I haven't had to split/rework event logic yet. I think there is a Full-Stack Radio podcast episode that went over that topic. Might have been one of these:

• http://www.fullstackradio.com/85
• http://www.fullstackradio.com/95

A good rule of thumb is set the value in your created or updated event unless:

• It is a state change
• An existing attribute is being mutated based on previous data

The above considerations have worked well for me thus far.

from laravel-event-sourcing.