We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey,
I believe having the package resolve nested namespaces automatically would be a good feature.
For example:
So take a component in the namespace:
namespace ClockingSystems\Auth\Livewire\Pages;
Then in the config file we'll define this:
'class_namespaces' => [ 'clocking-systems.auth' => 'ClockingSystems\\Auth\\Livewire', ],
This will give this error when using a full page component:
Unable to find component: [clocking-systems.auth-login]
Changing the namespace to include the pages namespace will allow it to work:
'class_namespaces' => [ 'clocking-systems.auth' => 'ClockingSystems\\Auth\\Livewire\\Pages', ],
I believe it should work like this
Which allows use of components in nested namespaces such as
<livewire:clocking-systems.auth.pages.login/> <livewire:clocking-systems.auth.modals.forgot-password/>
This is how the livewire component discovery works by default
The text was updated successfully, but these errors were encountered:
joserick
No branches or pull requests
Hey,
I believe having the package resolve nested namespaces automatically would be a good feature.
For example:
So take a component in the namespace:
Then in the config file we'll define this:
This will give this error when using a full page component:
Changing the namespace to include the pages namespace will allow it to work:
I believe it should work like this
Which allows use of components in nested namespaces such as
This is how the livewire component discovery works by default
The text was updated successfully, but these errors were encountered: