This article will take you through the feature templates and root templates in Angular. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to everyone.
The premise is that Angular cli is installed. Most of the following file creation depends on cliProvided directives
<span style="font-size: 20px;">Angular</span>The attribute template and root template (<span style="font-size: 20px;">AppModule</span> )
The difference is that feature templates can divide applications. My personal understanding is similar to componentization
1. Feature templates The created command ng g module article, here is ng g module article --routing, which can generate a article-routing.module.ts routing file
2. At this time, CLI will create another folder article, article file under the app folder The folder contains two files article.module.ts and article-routing.module.ts
3. Use ng g component to generate For two components, the specified template is article. The specified template will be automatically imported into article.modules.ts and registered in the declarations array, Note: Do not delete the components registered in declarations, otherwise some specifications in the components will become unusable
ng g component article/article-list -m=article, generate article-list folder component folder ##ng g component article/article-create -m=article, generate article-create folder component## under the article
In the feature module generated by the CLI, there are two JavaScript import statements at the top of the file: the first imports NgModule, which The same as in the root module allows you to use the @NgModule decorator; the second one imports CommonModule, which provides many functions like ngIf and ngFor Such common instructions. Feature modules import CommonModule, not BrowserModule, which should only be imported once in the root module. CommonModule only contains information about commonly used directives, such as ngIf and ngFor, which are used in most templates, while BrowserModule Application configurations made for the browser are only used once. <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class="brush:php;toolbar:false">import { NgModule } from &#39;@angular/core&#39;;
import { CommonModule } from &#39;@angular/common&#39;;
import { ArticleRoutingModule } from &#39;./article-routing.module&#39;;
import { ArticleListComponent } from &#39;./article-list/article-list.component&#39;;
import { ArticleCreateComponent } from &#39;./article-create/article-create.component&#39;;
@NgModule({
declarations: [ArticleListComponent, ArticleCreateComponent],
imports: [
CommonModule,
ArticleRoutingModule
]
})
export class ArticleModule { }</pre><div class="contentsignin">Copy after login</div></div>Related recommendations: "
, routing address nested configuration, here The address setting is because the routing prefix of the current module has been set to article in the app-routing.module root routing module, so the following routes can only be set directly. Visit with the routing prefix set by the root route.
list, and the access address needs to be article/list
import { NgModule } from '@angular/core'
import { Routes, RouterModule } from '@angular/router'
import { ArticleListComponent } from './article-list/article-list.component'
import { ArticleCreateComponent } from './article-create/article-create.component'
const routes: Routes = [
{
path: '',
children: [
{
path: '',
pathMatch:'full',
redirectTo: '/article/list'
},
{
path: 'list',
component: ArticleListComponent
},
{
path: 'create',
component: ArticleCreateComponent
}
]
}
]
@NgModule({
imports: [RouterModule.forChild(routes)],
exports: [RouterModule]
})
export class ArticleRoutingModule {}, import the app-routing.module file to configure global routing <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class="brush:php;toolbar:false">import { HttpClientModule } from &#39;@angular/common/http&#39;;
import { NgModule } from &#39;@angular/core&#39;;
import { FormsModule } from &#39;@angular/forms&#39;;
import { BrowserModule } from &#39;@angular/platform-browser&#39;;
import { AppRoutingModule } from &#39;./app-routing.module&#39;
import { AppComponent } from &#39;./app.component&#39;;
@NgModule({
declarations: [
AppComponent
],
imports: [
BrowserModule,
FormsModule,
HttpClientModule,
AppRoutingModule
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }</pre><div class="contentsignin">Copy after login</div></div>7. The routing of the root module
loadChildren uses the lazy loading feature module. By default, NgModule is Urgently loaded, which means it will be loaded as soon as the application loads, this is true for all modules, regardless of whether they are needed immediately or not. For larger applications with many routes, consider using lazy loading - a pattern of loading NgModule on demand. Lazy loading reduces the initial bundle size and therefore load time. <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class="brush:php;toolbar:false">import { NgModule } from &#39;@angular/core&#39;
import { Routes, RouterModule } from &#39;@angular/router&#39;
import { LoginComponent } from &#39;./login/login.component&#39;
const routes: Routes = [
{ path: &#39;login&#39;, component: LoginComponent },
{
path: &#39;article&#39;,
loadChildren: () => import(&#39;./article/article.module&#39;).then((m) => m.ArticleModule)
}
]
@NgModule({
imports: [RouterModule.forRoot(routes)],
exports: [RouterModule]
})
export class AppRoutingModule {}</pre><div class="contentsignin">Copy after login</div></div>8. Finally, if you want to access the
and create routes below article, enter the address article/list in the browser
The above is the detailed content of Detailed explanation of Angular root module and feature module. For more information, please follow other related articles on the PHP Chinese website!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
