mirror of
https://github.com/archtechx/laravel-tips.git
synced 2025-12-12 21:34:03 +00:00
16 lines
No EOL
540 B
Markdown
16 lines
No EOL
540 B
Markdown
---
|
|
title: 'Consider single-action controllers'
|
|
tweet_id: '1272826438891298816'
|
|
thread_slug: laravel-clean-code-tactics
|
|
author_username: samuelstancl
|
|
images:
|
|
- 'https://pbs.twimg.com/media/Ean6Sn9XkAA-WKS.png'
|
|
created_at: 2020-06-16T09:40:45+00:00
|
|
slug: consider-single-action-controllers
|
|
---
|
|
|
|
If you have a complex route action, consider moving it to a separate controller.
|
|
|
|
For OrderController::create, you'd create CreateOrderController.
|
|
|
|
Another solution is to move that logic to an action class — do what works best in your case. |