[Bug]: `route()` helper not targeting related component

[ghabriel25]

Extension Version

1.5.1

PHP Binary

Herd

Operating System

Windows

What happened?

route() helper show livewire route resolver instead the component itself or at least the route where its defined

[N1ebieski]

@ghabriel25 I can't reproduce this bug. Do I need to install something?

[ghabriel25]

@N1ebieski Its Livewire 4 route for mfc

// resources/views/pages/images/images.php
// resources/views/pages/images/images.blade.php

Route::livewire('/images', 'pages::images')->name('images.index');

If its still not enough to reproduce the bug, I'll post my extension (however Im pretty sure they are not related to livewire route

[N1ebieski]

Hmm is it a bug? The route helper always links to the controller, while the view helper links to the component's view.

[ghabriel25]

So it cant be targeting the component? For class based If remember correctly, its targeting the class (is it Livewire 3?)

[N1ebieski]

The problem is:

Route::livewire('/images', 'pages::index')

pages::index links directly to the component's view.

The route helper always links to the controller/component class.

In Livewire 3 it worked because every component class is registered as a controller, for example:

Route::get('/images', ImagesComponent::class)->name('images.index');

<?php

namespace App\Livewire;

use Livewire\Component;

class ImagesComponent extends Component
{
    public function render()
    {
        return view('pages::index');
    }
}

[ghabriel25]

I see, so its for class based only.

In Livewire 3 it worked because every component class is registered as a controller

So, anonymous component class (MFC) cant be treated like that?