This is exactly how all my laravel controllers are coded. 🧼

Exactly how I’m structuring my controller method arguments - follow the data through the request lifecycle 🤙🏻

🧼

naming the Action var $action is one of the smoothest move I learnt from you :D

🫡

Joining an existing project and seeing this, the baby in my womb jumps for joy! Only difference is my actions use the `Dispatchable` trait, which lets me do: Action::dispatch(...)

been using this pattern, business logic should reside inside the action/service class, controller is more cleaner and easy to do a unit test. ✅

These snippets are gold.

Only thing I do extra is pass a dto to my actions, rather than an array or any of type of primitive. I also make my actions invokable but that’s personal choice. Well. I guess it all is really 😂

And do you use both authorization and verification in the form request? Do you create a nit test for this form request?

Yes, authorization on my form requests. I typically test form requests on my *ControllerTest.