(05-27-2015, 08:24 AM)mwhitney Wrote: Everything with HMVC (and modularization in general) tends to come down to what Narf said. If your module works on its own, you're fine. If your module requires another module in order to work properly, then something's wrong (I'm guilty of this myself in some of my older code).
If you do have a dependency on another module, but can't merge the dependent modules for some reason, they need to work properly without the other module(s). What this means depends on what the modules are doing for one another, but, in the end, it comes down to either failing gracefully or providing another means of fulfilling the request.
I am not understanding this. If you have an Auth Module, most likely every module in your app might require it.
Are you talking controller to controller calls or a view calling different controllers?
I really do not understand the correct way to use HMVC and would love to see a tutorial.
