Repeating Responses: Base Controller or Trait?

You forgot return statement in your store method.

When would you use a base controller and when would you use a trait?

In the case of API Responses, I use a Macro function using the Response class (based on one of your videos). It's another solution to not repeating the responses. Is it a good option? Or is just another option to solve the same "problem"?

Found very useful. Thank you.

What about using trait but only on the desired class such as (UsersController.php) not on the general parent Controller.php because it will be generally extended on all controllers which might not need or use these API methods.

does Laravel's [https://laravel.com/docs/10.x/eloquent-resources#resource-responses] response now resolve that trait / controller question ? i.e.** php artisan make:resource UserResource** then use that as static in route, jobs, etc.

Route::get('/user/{id}', function (string $id) { return new UserResource(User::findOrFail($id)); });