laravel:controller-cleanup

To refactor a bloated Laravel controller, extract validation into Form Requests, move business logic to Action or Service classes utilizing DTOs, and adopt resource or single-action controller patterns. This reduces controller bloat and enhances testability.

The best way to organize Laravel controllers is by extracting business logic into dedicated Action or Service classes and using Data Transfer Objects for clean data transfer between layers. This separation creates leaner, specialized controllers.

Form Requests reduce Laravel controller bloat by offloading authorization and validation logic from the controller into dedicated request classes. This keeps controllers focused on orchestration rather than data validation rules.

Use single-action controllers in Laravel when a controller handles only one specific action, promoting controller specialization. This pattern fits well with extracted Actions and DTOs, resulting in cleaner, more maintainable code.

Pass data between Laravel controllers and services using Data Transfer Objects. DTOs facilitate clean data transfer between layers, ensuring typed structured data flows from controllers to extracted Action or Service classes.

Yes, using DTOs with extracted Laravel Actions improves testability by isolating business logic into dedicated classes with structured data inputs. This allows you to test Actions independently of the controller and HTTP request lifecycle.