Best practices
To keep consistency in your application organization we recommend following a few set of best practices when working with actions.
Start with a verb
Name your action classes as concise, explicit phrases starting with a verb. For instance, an action responsible for sending a password reset email to the user could be named SendResetPasswordEmail.
Following this practice, your folder structure naturally becomes a clear catalog of all the features your application offers. This leads us to the next recommended convention.
Categegorize you actions
When your application start getting bigger you might end up with a really large actions folder. Don't be scared to categorize them in subfolders, autoloading will still work.
login_user.ts
register_user.ts
reset_user_password.ts
create_checkout_session.ts
update_payment_method.ts
create_user.ts
delete_user.ts