angular-routing

问题 Issue We get an error cannot find module in case following structure. app-routing.module.ts const routes: Routes = [ { path: CHILD_MANAGEMENT_PORTAL.baseUrl, canActivate: [AuthGuard], component: EnvelopeComponent, loadChildren: () => import('./features/child-management/child-management.module').then( m => m.ChildManagementModule ), data: { menuResolver: ChildManagementMenuResolver, pageTitleResolver: ChildManagementPageTitleResolver, portalData: CHILD_MANAGEMENT_PORTAL } }, ]; @NgModule({

问题 I'm having a weird bug while developing a basic app from scratch right now. I use Ionic 4 beta 19 and I've put a routerLink to another page, the route is set up in the base pages module like so: RouterModule.forChild([ { path: '', component: NewsPage }, { path: ':id', component: DetailPage } ]) the routerLink attribute is set on a card and it works just fine when clicking on a card, but when I go back and press that same card or another one, the router just doesn't do anything at all. I don't

问题 Is there a way to implement navigation history based breadcrumb instead of normal route path based breadcrumb. example Route : Home - HChild1 - HChild1.1 Home - HChild2 - HChild2.1 If user navigates to HChild2.1 from Home page breadcrumb should be Home | HChild2.1 instead of Home | HChild2 | HChild2.1 Then if user navigates to HChild1.1 from HChild2.1 then breadcrumb should be Home | HChild2.1 | HChild1.1 instead of Home | HChild1.1 | HChild1.1 what I have is normal route path based

问题 Is there a way to implement navigation history based breadcrumb instead of normal route path based breadcrumb. example Route : Home - HChild1 - HChild1.1 Home - HChild2 - HChild2.1 If user navigates to HChild2.1 from Home page breadcrumb should be Home | HChild2.1 instead of Home | HChild2 | HChild2.1 Then if user navigates to HChild1.1 from HChild2.1 then breadcrumb should be Home | HChild2.1 | HChild1.1 instead of Home | HChild1.1 | HChild1.1 what I have is normal route path based

问题 I have angular 8 and a link that will create a new view. The current link is like this: http://localhost:4200/en/dossier/06637e72-8915-4735-9400-4ef7705194ea and the new view is like this: http://localhost:4200/en/dossier/06637e72-8915-4735-9400-4ef7705194ea/item/new/Interview But so I want that: ...\item/new/Interview will be loaded in the same view as: So replaced http://localhost:4200/en/dossier/06637e72-8915-4735-9400-4ef7705194ea So that the new will not be loaded in a totally new view.

问题 I have created an angular application version 7 and project structure is like this. app module have app-routing.module.ts and dashboard module have dashboard-routing module.ts. In dashboard module, the layout component route has child components namely home and admin. Here is my code: AppModule import { AppRoutingModule } from './app-routing.module'; import { DashboardModule } from './dashboard/dashboard.module'; import { AppComponent } from './app.component'; import { LoginComponent } from '

问题 I have created an angular application version 7 and project structure is like this. app module have app-routing.module.ts and dashboard module have dashboard-routing module.ts. In dashboard module, the layout component route has child components namely home and admin. Here is my code: AppModule import { AppRoutingModule } from './app-routing.module'; import { DashboardModule } from './dashboard/dashboard.module'; import { AppComponent } from './app.component'; import { LoginComponent } from '

问题 I have created an angular application version 7 and project structure is like this. app module have app-routing.module.ts and dashboard module have dashboard-routing module.ts. In dashboard module, the layout component route has child components namely home and admin. Here is my code: AppModule import { AppRoutingModule } from './app-routing.module'; import { DashboardModule } from './dashboard/dashboard.module'; import { AppComponent } from './app.component'; import { LoginComponent } from '

问题 I have facing a problem 404 page not found in production build when refresh a page. Build working fine with # routing RouterModule.forRoot(routes, { useHash: true }) . But I want a pretty route without # My module look like @NgModule({ declarations: [ AppComponent ], imports: [ BrowserModule, FormsModule, HttpClientModule, CoreModule, AppRoutingModule, AuthModule ], providers: [ { provide: HTTP_INTERCEPTORS, useClass: HttpInterceptorService, multi: true } ], bootstrap: [AppComponent] }) 回答1:

问题 I have facing a problem 404 page not found in production build when refresh a page. Build working fine with # routing RouterModule.forRoot(routes, { useHash: true }) . But I want a pretty route without # My module look like @NgModule({ declarations: [ AppComponent ], imports: [ BrowserModule, FormsModule, HttpClientModule, CoreModule, AppRoutingModule, AuthModule ], providers: [ { provide: HTTP_INTERCEPTORS, useClass: HttpInterceptorService, multi: true } ], bootstrap: [AppComponent] }) 回答1: