- Angular UI Development with PrimeNG
- Sudheer Jonna Oleg Varaksin
- 443字
- 2021-07-15 17:32:56
Components, services, and dependency injection
Normally, you write Angular applications by composing HTML templates with the Angular-specific markup and component classes to manage those templates. A component is simply a TypeScript class annotated with @Component. The @Component decorator is used to define the associated metadata. It expects an object with the following most used properties:
- selector: This is the name of the HTML tag representing this component
- template: This is an inline-defined template with HTML/Angular markup for the view
- templateUrl: This is the path to an external file where the template resides
- styles: An inline-defined styles to be applied to this component's view
- styleUrls: An array of paths to external files with styles to be applied to this component's view
- providers: An array of providers available to this component and its children
- exportAs: This is the name under which the component instance is exported in a template
- changeDetection: This is the change detection strategy used by this component
- encapsulation: This is the style encapsulation strategy used by this component
A component class interacts with the view through an API of properties and methods. Component classes should delegate complex tasks to services where the business logic resides. Services are just classes that Angular instantiates and then injects into components. If you register services at the root component level, they act as singletons and share data across multiple components. In the next section, Angular modularity and lifecycle hooks, we will see how to register services. The following example demonstrates how to use components and services. We will write a service class ProductService and then specify an argument of type ProductService in the constructor of ProductComponent. Angular will automatically inject that service into the component:
import {Injectable, Component} from '@angular/core';
@Injectable()
export class ProductService {
products: Product[];
getProducts(): Array<Product> {
// retrieve products from somewhere...
return products;
}
}
@Component({
selector: 'product-count',
template: `<h2 class="count">Found {{products.length}} products</h2>`,
styles: [`
h2.count {
height: 80px;
width: 400px;
}
`]
})
export default class ProductComponent {
products: Product[] = [];
constructor(productService: ProductService) {
this.products = productService.getProducts();
}
}
It is good to know what an item in the providers array looks like. An item is an object with the provide property (symbol used for dependency injection) and one of the three properties useClass, useFactory, or useValue that provide implementation details:
{provide: MyService, useClass: MyMockService}
{provide: MyService, useFactory: () => {return new MyMockService()}}
{provide: MyValue, useValue: 50}
- Mastering Entity Framework Core 2.0
- 摩登創客:與智能手機和平板電腦共舞
- 簡單高效LATEX
- C語言程序設計基礎與實驗指導
- PostgreSQL技術內幕:事務處理深度探索
- 區塊鏈:以太坊DApp開發實戰
- Python機器學習實戰
- SQL Server 2012數據庫管理與開發項目教程
- Mastering KnockoutJS
- SQL Server 2016數據庫應用與開發習題解答與上機指導
- Mastering Apache Spark 2.x(Second Edition)
- SQL Server從入門到精通(第3版)
- Apache Kafka Quick Start Guide
- 領域驅動設計:軟件核心復雜性應對之道(修訂版)
- Linux C編程:一站式學習