-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
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
ocLazyload will load already loaded component if application is launched by angular.bootstrap #109
Comments
When it says "moduleReloaded" it's just that it finds "sharedModule" listed as a dependence and it checks if anything new needs to be triggered (for example if you put the option "rerun" it will trigger the run block again, or if you loaded new components in the module it will register them), but it doesn't declare anything new that is not needed, so don't worry about that. |
But it reloads the
Sorry for the poor english that may misleads you :) |
Here is a more complete plunker that illustrates my problem. First click the "load lazyloadModule" to load the
|
Oh that's a bug that should be fixed :-/ |
Thanks for the fast response and your great work :) |
No problem, it's cool when someone takes the time to make a plunkr that I can use to reproduce the bug ! |
It's in 0.5.2, thanks for your help I fixed 3 bugs in one, and now you don't need to use loadedModules when you use angular.bootstrap, it just works :) |
bravo! |
I put a simple example in this plunker to illustrate the problem.
The application and
lazyloadModule
both require 'sharedModule'.But when loading
lazyloadModule
, the debug log illustrates that ocLazyLoad loadedsharedDirective
again.The confusing part is if i put
sharedDirective
in a sub module which required bysharedModule
like this:Then everything works fine.
The behavior described in this issue will only happen if the application is launched by
angular.bootstrap
The text was updated successfully, but these errors were encountered: