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
Our application is organized into multiple modules, with each module registering its own Livewire components. These components are primarily registered via the Livewire facade using Livewire::component. For example, a module named Document registers a component like document.drafts.create. Given the large number of components, we implemented an auto-discovery mechanism to register all Livewire components within a specified directory or namespace, which avoids redundant code and ensures consistent naming.
It would be amazing if we get auto completion for these components. Additionally, it would be helpful if we could click on the Livewire tags in the template to navigate directly to their definitions.
The text was updated successfully, but these errors were encountered:
Yep, it's not a standard method. However, the package does more or less the same thing. I absolutely agree with you that a solution is needed for all users, of course.
Maybe it is possible to build the auto-completion dynamically and depending on the components registered in the Livewire ComponentRegistry?
Feature Description
Our application is organized into multiple modules, with each module registering its own Livewire components. These components are primarily registered via the Livewire facade using
Livewire::component
. For example, a module named Document registers a component likedocument.drafts.create
. Given the large number of components, we implemented an auto-discovery mechanism to register all Livewire components within a specified directory or namespace, which avoids redundant code and ensures consistent naming.It would be amazing if we get auto completion for these components. Additionally, it would be helpful if we could click on the Livewire tags in the template to navigate directly to their definitions.
The text was updated successfully, but these errors were encountered: