Apa iki controller ing Laravel?

Question

Accepted Answer

**Controller** nglompokake logika panganan pamintaan sing ana maneh menyang kelas. Tinimbang gawe kabeh logika ing route closure, controller nggawe aksi aplikasi (contone kabeh operasi sing ana hubunge karo user) dadi metode — njaga route tetep resik lan kode terorganisir.

## Controller dasar

```php
<?php
class UserController extends Controller {
    public function index() {
        return User::all();              // list users
    }
    public function show(User $user) {   // route model binding — auto-fetch by id
        return $user;
    }
    public function store(Request $request) {
        $validated = $request->validate(['name' => 'required', 'email' => 'required|email']);
        return User::create($validated);  // create
    }
}
```

Gawe nganggo Artisan: `php artisan make:controller UserController`. Saben metode nangani siji aksi, lan route menunjok menyang padha.

## Resource controller (CRUD RESTful)

```php
// generate a controller with all 7 RESTful methods stubbed
// php artisan make:controller PostController --resource

Route::resource('posts', PostController::class);   // maps routes to the methods:
// index() create() store() show() edit() update() destroy()
```

Sewu **resource controller** nduweni metode CRUD standar, dipasangake karo `Route::resource` kanggo routing RESTful konvensional — boilerplate minimal kanggo sumber CRUD khas.

## Dependency injection ing controller

```php
class OrderController extends Controller {
    // type-hinted dependencies are AUTO-INJECTED by Laravel's service container
    public function __construct(private OrderService $orders) {}

public function store(Request $request, Mailer $mailer) {   // method injection too
        // $request and $mailer are resolved & injected automatically
    }
}
```

Service container Laravel **injeksi otomatis** dependensi sing ana tipe hint menyang konstruktor lan metode controller (kalebu `Request`) — kode resik lan bisa diuji.

## Urus controller tetep tipis

```text
✓ Controllers should handle HTTP concerns (validate input, call services, return responses)
✗ Business logic belongs in SERVICES/models, not bloated controllers ("thin controllers")
```

## Mengapa Penting

Controller yaiku blok pembangunan inti Laravel — nggawe logika panganan pamintaan menyang kelas kohesif, sing penting kanggo aplikasi apa pun ngisor rute trivial.

Paham carane gawe controller, pemetaan rute menyang metode padha, lan khususé nggunakake **resource controller** nganggo `Route::resource` (kanggo CRUD RESTful konvensional karo boilerplate minimal) yaiku kawruh saben dina kanggo bangun aplikasi Laravel.

Fitur kunci Laravel yaiku **injeksi dependensi otomatis** menyang controller liwat service container — dependensi sing ana tipe hint (layanan, pamintaan, mailer) nggawa maju lan injeksi otomatis, ngidupake kode resik, bisa diuji, lan ora erat kaiket.

Samané penting yaiku praktik terbaik njaga controller **tipis** — nangani mung kahanan HTTP (validasi, paggugone layanan, bali jawab) lan nyerahake logika bisnis menyang layanan/model, kang njaga kode bisa dirawat lan bisa diuji.

Controller, bareng karo routing lan model, mateng tulang punggung panganan pamintaan Laravel, nggawe padha basic kanggo bangun aplikasi Laravel sing terorganisir kanthi apik lan profesional.