I strongly disagree on removing the type hinting. You shouldn't have to extrapolate from the code in the function what to pass it and what you'll get back. By removing these type hints you're doing the exact opposite of your stated goal for this lesson.

The type hinting reduces the cognitive overhead of determining parameter and return types, which is especially useful in large and complex applications, which are where reducing cognitive overhead matters the most. Further, it reduces programmer error and enables modern IDEs to offer better inspections to catch errors while writing.

@Bionik6 my solution with Laravel 11 bootstrap/app.php file:

...
return Application::configure(basePath: dirname(__DIR__))
    ->withRouting(
        web: __DIR__.'/../routes/web.php',
        api: [// <-- we can use an array here
            __DIR__.'/../routes/api.php',
            __DIR__.'/../routes/api_v1.php',
        ],
        commands: __DIR__.'/../routes/console.php',
        health: '/up',
    )
...

and inside api_v1.php file:

...
Route::prefix('v1')->group(function () {
    Route::apiResource('tickets', \App\Http\Controllers\Api\V1\TicketController::class);
});
...

Been using PHPStorm for a while now and i'm absolutely loving it. Would wholeheartedly recommend it.

Hi @mozew Please explain your data structure further. From your console log i don't see where the related data / the actual items should be that you're trying to map over and render.