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
I just have an idea regarding the provders file inside bootstrap folder. We could make it a little dynamic to register all providers from the modules folder.
The configureModulesProviders method in src/Console/InstallerTraits/CoreModules.php adds the five Modular Core Modules (after Laravel’s App\Providers\AppServiceProvider) to bootstrap/providers.php. Because core modules do not tend to grow (extended functionality can be added by connecting modules) the existent declarative approach is easier to read and follow. It’s worth noting that, after installation, creating new modules with php artisan modular:make-module YourModuleName automatically registers the new module for you in bootstrap/providers.php, so there is no need to modify the installer for this use case.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Daniel,
Thank you for the ismodular project.
I just have an idea regarding the provders file inside bootstrap folder. We could make it a little dynamic to register all providers from the modules folder.
See my suggested idea below:
I am currently using this in my project and it is working really well.
Beta Was this translation helpful? Give feedback.
All reactions