Dive Deeper with Actions

In Jeffrey's recent Larabit ( • The Intermediate Devel... ) ,he discussed the intermediate trap and how you can use actions to keep code clean and understandable. You know, I'm something of an action man myself, so I'd like to take it one step further. Strap in, it's time for Action-ception.
Watch thousands of videos, track your progress, and participate in a massive Laravel community at Laracasts.com.
Laracasts: laracasts.com
Laracasts Twitter: / laracasts
Jeffrey Way Twitter: / jeffrey_way

[@relaxationtube2388]

Good lessons here.
Perhaps it’s beyond the scope of this Larabit but putting those magic numbers (experience points) into an enum or some sort of experience class will definitely improve this workflow

[@gdogmalone]

GREAT, video. Learnt loads 🙌

[@ParisBenjaminsound]

Thanks

[@obadaalzidi6452]

Thanks, that's great !
Just for clarity, shouldn't the AwardExperienceTest be a Unit test ?

[@VuTuanIT]

A unit test should be pure and not involve database transactions, otherwise, place it into feature tests

[@dragoninfintyskull]

Full course on actions with test please….

[@houseandhobby6971]

Oops I dropped in to learn about class action lawsuits to avoid the developer.

[@popforall]

What if I have a database transaction in some of my sub actions
Should I add another transaction to the parent actions or what should I do?

[@yoho403]

Wouldn't a trait be better in this case to avoid creating one time use objects?

[@mahmoud-bakheet]

You are the other Jeffrey either 😂

[@shamwela_]

Why don't you just create a reusable function instead of creating "Action" classes for every little thing that you want to do.

[@arash5094]

Please integrate in mongodb to next version of laravel you think it's time don't you