refactor-entry-point-to-action

To refactor a fat controller method into an Action class, you extract orchestration logic into a dedicated readonly Action with a single __invoke method, preserving original signatures, responses, and boundary-respecting reads while delegating validation.

The Action pattern extracts business orchestration from entry points like controllers and jobs into a final readonly class containing exactly one __invoke method, ensuring thin delegation and keeping database calls outside the Action.

Yes, you can use this refactoring approach for Livewire component methods and queued jobs. It applies to controllers, jobs, commands, and listeners, converting thick methods into thin delegates that call a single Action class.

Data validation should live in a dedicated Data Validator rather than inside the Action itself. When moving logic into a dedicated Action, you must extract inline validation out of the Action to follow project conventions.

The best way to handle Eloquent queries when refactoring entry points into Actions is to keep all database calls outside the Action entirely. The Action must contain no Eloquent or DB calls, relying instead on boundary-respecting reads and writes.