You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my app, I have two sets of Livewire components. Some within the app itself, and some coming from a package. I'm using your module to load those from the package like this:
Since the update from 1.0.0 => 1.3.1, number 2 only works if number 1 isn't called before it (in previous lines in the blade template).
Is there no support (anymore) for including livewire components under App\Livewire without an explicit prefix? I have tried setting an empty prefix, but this is not working either.
The text was updated successfully, but these errors were encountered:
I'm on a trip now but I'll check tomorrow and try to replicate the problem, in the meantime you can run php artisan livewire-discover:list to see if all external Livewires are loaded correctly, as Livewire-Discover is only called after checking that the class (file) you require does not exist inside App/Livewire.
If i run the livewire-discover:list command, it only shows the namespaced/prefixed (manually defined) items. I can of course add an entry like 'app' with namespace 'App\Livewire', but then I'd have to change code everywhere to app:some-local-class.
In my app, I have two sets of Livewire components. Some within the app itself, and some coming from a package. I'm using your module to load those from the package like this:
Livewire::componentNamespace('MyVendorName\MyPackageName\Livewire', 'vendorname');
Previously, using version 1.0.0 of your package, I could then use both of these
Since the update from 1.0.0 => 1.3.1, number 2 only works if number 1 isn't called before it (in previous lines in the blade template).
Is there no support (anymore) for including livewire components under App\Livewire without an explicit prefix? I have tried setting an empty prefix, but this is not working either.
The text was updated successfully, but these errors were encountered: