Comments & Discussion
Hi! First of all, thank you very much for your amazing videos. They are very much helpful to reorganize my coding viewpoints and improvement.
I am going to build a project where there will be 3 kinds of user portal (e.g user-A, user-B, admin). The client wishes for the User portal A & B should be developed as SPA (preferable reactJS). As there will be few admins, he does not care whether the Admin panel is built on blade or SPA.
I am thinking to use Inertia/ReactJS for user A & B portal and Laravel Modules for architecture.
I have good experience in ReactJS as well as Laravel Module implemetations separately, but I haven't used them in a single project.
I am thinking each module will hold the all the Admin related MVC and User related APIs & Inertia routes. The reactJS source code will be inside the resource folder of course.
Is my approach good? If so, is there anything important issue I need to know during development phase?
Hi!, We have an API project where we are using this pakage "laravel-modules". We would like to separate the logic for our own core modules (folder Modules\Core) and customized and optional modules (folder Modules\Extend) depending on the client needs. It would be interesting to know how to manage and organise something like this. Since version 9.0.2 of the package the possibility is included, but there is not much documentation and nothing in the case you have to migrate the modules already created in Modules folder to subfolders (as it is our case moving modules from Modules to Modules\Core). Thanks very much!
I guess this would be a question to the package creator, so you should raise this on their GitHub issues. I don't have experience enough with that package to answer your question, sorry.
You are right. Thanks for answering anyway. In case someone reads this I am just going to point out that the feature to support submodules was retired shortly after as well as the versions that included it.