uteq / laravel-model-actions Goto Github PK

The current behavior of this package is find actions that are close at a specific path. The user should have more control over this than changing the namespace.

I imagine some people would like to have an immediate reference to there Action class. In retrospect to using this approach:

$user->action('update', $input)

You would dot this

use App\Actions\User\Update;

$user->action(Update::class, $input)

At first this would seem counter intuitive. Why not instantiate the action class and perform the action?
app()->make(Update::class)($user, $input)

First I think this $user->action(Update::class, $input) is easier on the eyes and easier to comprehend what is happening.

Still, adding the Action classes to the model will give you more control over the actions from the perspective where you would like to use it most. If you for example would like to add some additional logic to your Actions specific for your User model, not having the actions on the model would make this a lot harder, and less DRY, because you would either have to create a Trait or a Class that all the Action classes would use.

The biggest benefit of being able to reference the class from wherever you call the action makes your workflow a lot easier. Especially when using a proper IDE.