laravel:controller-cleanup

To slim down Laravel controllers, move validation and authorization into dedicated Form Requests and delegate business logic to small Actions or Services using DTOs. This reduces controller bloat and centralizes request handling.

The best way to organize Laravel validation and authorization is to move them into dedicated Form Request classes. Type-hinting these Form Requests in controller methods ensures validation runs automatically before the action executes.

To pass data to Laravel Actions using DTOs, extract business logic into Actions or Services and pass DTOs directly from the Form Requests. This keeps controllers thin and maintains a structured data flow across requests and actions.

Yes, this Laravel refactoring approach supports resource controllers and single-action invokable controllers. Preferring these controller types simplifies orchestration and testing while keeping the controller layer thin.

To test Laravel Actions and Form Requests, write feature tests for the routes and unit tests for the extracted Actions or Services. This separation makes testing easier by isolating business logic from HTTP request orchestration.

You should extract Laravel controller logic into separate Actions when controllers become bloated with business logic. Moving this logic to small Actions or Services that accept DTOs improves testability and reduces controller bloat.