0028-laravel-controllers

What problem does it solve?

It prevents bloated Laravel controllers by ensuring HTTP endpoints only orchestrate request/response flow while domain logic lives elsewhere.

Core Features & Use Cases

• Thin controller structure: Type-hint dependencies, rely on Form Requests for validation, call actions for behavior, and return resources/views with no business rules.
• Correct controller conventions: Use plural naming, RESTful method names only, and extract non-REST endpoints into invokable controllers.
• API list/query hygiene: Delegate filtering, sorting, and includes to Query Objects so controllers stay consistent and maintainable.

This fits teams building Web vs Public API layers, standard REST endpoints, and endpoints that need flexible API filtering without turning controllers into query-and-calculation dumping grounds.

Quick Start

Follow the guide to create or refactor your Laravel controllers so they validate via Form Requests, call Actions for domain logic, and return Resources or views while moving filtering and sorting into Query Objects.