Add Eloquent Model Event Handling Attributes e.g. #[Listener('created')]

[marvinosswald]

Handling Events with listeners on your Model with lifts fantastic syntax, Thanks for making this library IMHO this should be part of the framework seems like a no-brainer to me ever since I saw Caleb's talk on Laracon Us this year.

This PR supports every Model Event documented.

Listener

#[Listener(queue: true)]
public function onUpdated(Product $product): void
{
    Log::info('onUpdated has been called');
}

#[Listener('updated')]
public function handleUpdatedEvent(Product $product): void
{
    Log::info('onUpdated has been called');
}

Observer

#[Observer(UserObserver::class)]
class User extends Authenticatable
{
    use HasFactory;
    //...
}

Dispatches

#[Dispatches(UserSaved::class, 'saved')]
class User extends Authenticatable
{
    use HasFactory;
    //...
}

Convention based

#[Dispatches(UserSaved::class)]
class User extends Authenticatable
{
    use HasFactory;
    //...
}

[WendellAdriel]

Hey @marvinosswald thanks for the kind words!
Thanks for the PR!

Can you provide some examples showing how these attributes would be better than the current syntax with some real life examples? Please create a discussion in the Ideas category for that and add the link of this PR there, so we can discuss there!

[marvinosswald]

@WendellAdriel i've incorporated naming changes we discussed as well as adding queuable for Listeners

And because i like laravels general approach of overridable convention, we can now use #[Listener] without passing an explicit event name if the function name is prefixed with on and camel cased.

For custom event dispatching i did the same you can register events like this #[Dispatches(ProductSaving::class, 'saving') or just #[Dispatches(ProductSaving::class) which works if Saving can be found in the event name.

If you feel like those convention based usages are to ambigious let me know and i remove them again, just felt so much more comfortable to me.

[WendellAdriel]

I just made some observations regarding the code.
Also, since this is a new feature with a lot of details, can you also create a PR in the docs repo for it, please?

[marvinosswald]

@WendellAdriel i'll be working on a docs PR, i'll prepare a PR based on unchecked Markdown. Please advice if there is a better possibility with gitbooks, thanks.

[marvinosswald]

@WendellAdriel created a PR on the docs repo for this: WendellAdriel/laravel-lift-docs#2

[WendellAdriel]

All good here! 🔥

[WendellAdriel]

I'm going to merge this but I'll wait for the docs to be ready to release the new version!
Thanks for the contribution @marvinosswald!!! 🔥 💪