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
From the Angular docs it looks like the only difference between them is that forRoot includes the Router service. You're right that it seems we should use.forChild. It's not that clear why though
Only call RouterModule.forRoot in the root AppRoutingModule (or the AppModule if that's where you register top level application routes). In any other module, you must call the RouterModule.forChild method to register additional routes.
I asked on JHipster's Gitter. Maybe someone else knows.
Hi!
For what reason do you use
RouterModule.forRoot(...)
in all modules, and not just in the main?The text was updated successfully, but these errors were encountered: