How to Get URL Segment in Laravel?

-

How to Get URL Segment in Laravel?


   
     In this article, We will learn to get URL segments in controller and blade using the Laravel.


Example 1 : 

  • Get URL Segments in Controller 
  <?php 

     namespace App\Http\Controllers;

     use Illuminate\Http\Request;

     class BlogController extends Controller
     {
         public function index(Request $request)
         {
              //add parameter in segment function to get specific segment
             // $segments = $request->segments(1);
             $segments = $request->segments();

             dd($segments);
         }
     }
Example 2 :

  • Get URL Segments in Blade File 
  <?php

    namespace App\Http\Controllers;

    use Illuminate\Http\Request;

    class BlogController extends Controller
    {
       public function index()
       {

          //add parameter in segment function to get specific segment
          // $segments = Request::segments(1);
          $segments = Request::segments();

          dd($segments);
       }
   }
That's it....😊😀😀

Comments

Post a Comment

Popular Posts

I Let AI Write My Laravel Service Layer — It Worked… Until I Understood What It Actually Did

-
Image
I tried something dangerous. I asked AI to generate a full Laravel service layer: Repository Service class DTO Validation Controller Tests It generated everything in seconds. Clean code. Solid structure. Proper dependency injection . At first, I was impressed. Then I looked deeper. 🤖 The Illusion of Architectural Intelligence AI generated this:     class OrderService     {         public function __construct (             protected OrderRepository $repository         ) {}         public function create ( array $data ): Order         {             return $this -> repository -> create ( $data );         }     }     Looks clean. But notice something subtle: The service is just forwarding calls. No business boundaries . No domain modeling . Just ab...
Read more

Laravel Time Machine: Find Where Your Laravel Request Is Spending Time

-
Image
  Have you ever looked at a slow Laravel request and wondered: “Where exactly is the time going?” Is it middleware? Routing? Controller logic? Database queries? An external API? I built Laravel Time Machine to make answering that question easier. What is Laravel Time Machine? Laravel Time Machine is a lightweight request lifecycle profiler for Laravel. Instead of adding microtime() calls throughout your code or trying to guess where the bottleneck is, it gives you a visual timeline of the request lifecycle. You can see: 🚀 Application boot time 🔐 Middleware execution 🛣️ Routing 🎯 Controller execution 🗄️ Database queries 📤 Response handling ⏱️ Request termination 💾 Memory usage 🐌 Slow requests and queries The project is open source and currently supports Laravel 8 through 13. Why I built it When debugging performance issues, developers often start adding temporary timing code: $start = microtime(true); // Some code... logger(microtime(true) - $start); It works, but it bec...
Read more

How Laravel’s Service Container Resolves Dependencies Automatically

-
Image
 One of the most powerful but least fully understood parts of Laravel is the Service Container . Many developers use it every day without realizing it. Every time Laravel automatically injects a dependency like this:     public function __construct ( UserService $userService )     {         $this -> userService = $userService ;     } Laravel is using its Service Container to resolve the dependency automatically. But how does this actually work internally? Let's go deeper. 🧩 What Is Laravel's Service Container? Laravel’s Service Container is essentially an advanced dependency injection container . It handles: Class instantiation Dependency resolution Interface binding Singleton management Automatic dependency injection Internally, it relies heavily on PHP Reflection . 🔍 Example: Automatic Dependency Resolution Imagine we have a service:          class PaymentService ...
Read more