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
If breadcrumb component is called from template in child route <breadcrumb></breadcrumb> , where we have defined <router-outlet></router-outlet> it doesn't have any of URLs registred and therefore, breadcrumbs doesn't display anything. However if we navigate somewhere inside application, it's starts working.
For example here is the list of defined routes in application:
However if we would make same call inside ServicesComponent, which is child route which has registred other children routes, described issue will appear.
Why I would like to call it inside child components and not from the root direclty, is because I want to have breadcrumbs displaying it only there on Services components. Calling hideRoute(route: string) function from breadCrumbService can't help in this case since security pages have completely different HTML then services pages.
The text was updated successfully, but these errors were encountered:
If breadcrumb component is called from template in child route
<breadcrumb></breadcrumb>
, where we have defined<router-outlet></router-outlet>
it doesn't have any of URLs registred and therefore, breadcrumbs doesn't display anything. However if we navigate somewhere inside application, it's starts working.For example here is the list of defined routes in application:
If we would call a breadcrumb component inside app,component.html, where we have first call of router-outlet everything will work:
However if we would make same call inside ServicesComponent, which is child route which has registred other children routes, described issue will appear.
Why I would like to call it inside child components and not from the root direclty, is because I want to have breadcrumbs displaying it only there on Services components. Calling hideRoute(route: string) function from breadCrumbService can't help in this case since security pages have completely different HTML then services pages.
The text was updated successfully, but these errors were encountered: