Piye cara routing ing Laravel?

Question

Accepted Answer

**Routing** nggoleki URLs lan HTTP methods menyang kode sing nangani. Ing Laravel sampeyan nggawe routes ing file routes (`routes/web.php`, `routes/api.php`) nggunakake facade `Route`, nuding saben menyang closure utawa method controller. ## Routes dhasar ```php 'Home'); // GET / → closure Route::get('/users', [UserController::class, 'index']); // → controller method Route::post('/users', [UserController::class, 'store']); // POST Route::put('/users/{id}', [UserController::class, 'update']); Route::delete('/users/{id}', [UserController::class, 'destroy']); ``` Saben HTTP method nduwe helper `Route::`. Routes nuding menyang closure (kanggo kasus sederhana) utawa, luwih umum, pasangan `[Controller::class, 'method']`. ## Parameter route ```php Route::get('/users/{id}', function ($id) { // {id} captured and passed in return User::find($id); }); Route::get('/posts/{post?}', fn($post = null) => ...); // optional parameter ``` ## Routes jeneng (ngrujuk routes miturut jeneng, dudu URL) ```php Route::get('/profile', [ProfileController::class, 'show'])->name('profile'); // generate URLs by NAME — refactor-safe (change the URL in one place) route('profile'); // → "/profile" redirect()->route('profile'); // in Blade: Profile ``` **Named routes** ngidini sampeyan ngrujuk routes miturut jeneng ing sapisan ngganti hardcoding URLs — dadi ngganti URL ora pecah link (praktik DRY, isa dirawat). ## Grup routes lan resource routes ```php // group routes with shared middleware/prefix Route::middleware('auth')->prefix('admin')->group(function () { Route::get('/dashboard', ...); // → /admin/dashboard, requires auth }); // resource routes — all 7 RESTful routes for a controller at once Route::resource('posts', PostController::class); // → index, create, store, show, edit, update, destroy automatically ``` `Route::resource` ngasilake set lengkap routes RESTful kanggo controller — kode minimal kanggo CRUD standar. ## Apa iya penting Routing minangka dhasar saben aplikasi Laravel — iku nagawe URLs aplikasi lan nggubung menyang handler, dadi paham iku ilmu saben dinten kanggo bangun endpoint apa wae. Katrangan pira-pira define routes kanggo saben HTTP method, capture parameter, nuding routes menyang controller, lan atur karo grup (kanggo shared middleware/prefix) iku perlu kanggo struktur aplikasi. Praktek loro iku luwih penting: **named routes** (ngrujuk routes miturut jeneng tinimbang hardcoded URLs — katon penting kanggo isa dirawat sing njaga link ora pecah manawa URLs owah), lan **resource routes** (`Route::resource`, sing ngasilake kabeh routes RESTful standar kanggo controller karo siji baris — feature produktivitas gede kanggo CRUD). Routing nggubung titik mlebu (URLs) menyang logika aplikasi (controller), dadi inti, materi sing kudu karep kanggo bangun aplikasi Laravel sing terstruktur apik, lan konvensi named-route lan resource-route nggambarake tekanan framework ing design bersih, DRY, RESTful.