One of my first ideas was if an event could have a Deferrable or NonDeferrable attribute, until I remembered that a lot of laravel events are just pure strings which is why I withheld suggesting it, but maybe could be an avenue to explore in the future. Unless maybe a pattern matching could be defined for string events like maybe Event::defineNonDeferrable('eloquent.creating: *'), but it would make sense, in my opinion, to have Model creating, updating etc. non-deferrable by default, as they can also prevent creating or updating a Model.

I like the pattern matching idea... not sure about globally defining it... Let's wait for more feedback

@dbpolito Hello, can you document the Deferred Events new concept?

Do you think there would be an easy way to only defer -ed events? so creating, which may modify an attribute before it's saved, would pass through, but created would wait until the defer block is complete?

I don't think I have a use case for this in mind just yet, however, I would think about something like Spatie's medialibrary, which only creates the UUID on the model creating event. Obviously, this is a bit of a relic, given that we have HasUuids trait now, but nonetheless, seems like it could give some developers headaches.