The next step is to load the same "It works" but from the Blade file, and we will see how to register our View in the Service Provider.
First, we create the file itself:
packages/laraveldaily/laravel-permission-editor/resources/views/roles/index.blade.php:
It works from Blade!Then, we need to register the views to be loaded from that location. Again, as in other configurations, it's done in a Service Provider...
Why the directory resources/ is outside of the src/ directory? Is this because of any convention? or any other reason?
The same reason why resources/ folder is outside of the app/ directory in default Laravel project structure. Yes, it's Laravel convention.
Got it! Thank you Povilas. Great course. I've just published my first Laravel package core45/system-settings-db
What would be the approach if the use case was Livewire (layouts, components) instead of the default Laravel blade views? I managed to make it semi-work (it does render the Livewire layout + the component) but after using wire:click to trigger a method I get "Unable to find component:" error.
Is it compulsery to have the controllers also in app folder?
And I get 404 while trying to view the pages. What should be the issue?
Hi,
What do you mean by this?
Unregistered routes.