Laravel Routing Basics

# CHAPTER 4

Laravel Routing Basics #

1. Introduction #

2. Learning Objectives #

• Define basic GET and POST routes.

• Return a View directly from a route.

• Capture dynamic URL parameters (e.g., /user/5).

• Use Named Routes to prevent broken links.

3. Beginner-Friendly Explanation #

4. Basic Routing (GET and POST) #

A GET Route (Visiting a page):

use Illuminate\Support\Facades\Route;

// When a user visits www.site.com/hello
Route::get('/hello', function () {
    return 'Hello, Welcome to Laravel!'; // Returns plain text
});

Returning a View: Instead of plain text, we usually return a beautiful HTML View.

// When a user visits www.site.com/about
Route::get('/about', function () {
    // This looks for resources/views/about.blade.php
    return view('about'); 
});

5. Dynamic Route Parameters #

// The {id} acts as a wild-card placeholder
Route::get('/user/{id}', function ($id) {
    return 'Now viewing user profile number: ' . $id;
});

// Multiple Parameters
Route::get('/post/{post_id}/comment/{comment_id}', function ($post_id, $comment_id) {
    return "Viewing comment $comment_id on post $post_id";
});

6. Fallback Routes (Custom 404 Pages) #

Route::fallback(function () {
    return view('errors.custom_404'); // Render your custom HTML
});

7. Named Routes (The Best Practice) #

In web.php:

// We name the route 'profile.show'
Route::get('/account/my-profile-page', function () {
    return view('profile');
})->name('profile.show');

In your HTML (Blade) View:

<!-- Generate the URL dynamically using the route() helper function -->
<a href="{{ route(&#039;profile.show') }}">Go to Profile</a>

*Why this is magic:* If your boss changes the URL to /my-cool-account, you only change it in web.php. Because the HTML link relies on the nickname (profile.show), every single link on your website instantly updates automatically!

8. Backend Workflow: Routing to a Controller #

use App\Http\Controllers\UserController;

// When a user visits /users, hand the traffic to the 'index' method of UserController
Route::get('/users', [UserController::class, 'index']);

*(We will cover this deeply in the next chapter).*

9. Best Practices #

• Always Use Named Routes: Never hardcode URLs like <a href="/about"> in your views. Always use <a href="{{ route('about') }}">. It will save you from catastrophic link breakage when you redesign your site.

10. Common Mistakes #

• Method Not Allowed Error: If you create an HTML form with method="POST", but your web.php file defines the route as Route::get('/submit'), Laravel will crash and throw a 405 Method Not Allowed exception. POST traffic must be caught by a Route::post().

11. Exercises #

1. 1. Write a dynamic route that captures a string {category} and a number {id}, and returns text saying: "Viewing Category: X, Item: Y".

12. Coding Challenges #

• Challenge: Open routes/web.php in a Laravel project. Create a route for /contact that returns a view. Name the route contact.us.

13. MCQs with Answers #

14. Interview Questions #

• Q: Explain how dynamic routing parameters work in Laravel. How do you pass an ID from the URL into the route's closure or controller?

• Q: Differentiate between Route::get and Route::post. Give an example of a user action that would require each.

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #