Challenge 3: Fix Middleware That Never Calls $next() — Possible Solution
====================================================================

// BROKEN — never calls or returns $next($request)

namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;

class LogRequests
{
    public function handle(Request $request, Closure $next)
    {
        logger()->info("Incoming request: {$request->path()}");
        // ⚠️ missing: return $next($request);
    }
}

// FIXED

namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;

class LogRequests
{
    public function handle(Request $request, Closure $next)
    {
        logger()->info("Incoming request: {$request->path()}");
        return $next($request);
    }
}

WHAT HAPPENS WHEN A REQUEST PASSES THROUGH THE BROKEN VERSION
--------------------------------------------------------------------
The handle() method runs its logging line, then implicitly returns null
(since there's no explicit return statement) — Laravel expects handle()
to return an HTTP response, so returning null means the request never
reaches $next($request) at all. Concretely:

1. The actual route/controller this middleware sits in front of NEVER
   RUNS — no controller method executes, no database queries happen, no
   view gets rendered.
2. Any middleware defined AFTER this one in the pipeline also never runs,
   since $next($request) is what invokes the next layer.
3. The visitor typically sees either a blank page, a generic error (PHP
   may throw a TypeError since a Response object was expected but null
   was returned), or in some configurations an empty 200 response with no
   body — none of which clearly points to "a middleware forgot to call
   $next()" as the actual cause.

This is a genuinely tricky bug to diagnose precisely because there's no
loud error message saying "middleware X forgot to continue the
pipeline" — the visible symptom (page doesn't load, or loads blank) could
plausibly be blamed on the route, the controller, or the view, when the
actual defect is one missing line in a middleware class that otherwise
looks completely reasonable.

WHY THIS WORKS
--------------
- $next($request) is what actually invokes the NEXT layer of the
  pipeline — whether that's another middleware or, if this is the last
  one, the route's controller method itself. Skipping this call means
  everything downstream of this middleware simply never executes.
- return $next($request) does two things at once: it calls the next
  layer AND propagates whatever response that layer eventually produces
  back up through this middleware — omitting the `return` keyword (even
  if $next($request) were called) would still break the pipeline, since
  the response would be computed but then discarded rather than passed
  back to the caller.
- This is the Laravel-specific version of the exact same category of bug
  Express's `next()` middleware pattern and Django's `get_response(request)`
  closure call both share — every middleware system built on this
  "chain of responsibility" pattern has the same failure mode if the
  chain isn't explicitly continued.