Angular: Difference between revisions

From Wiki RB4
Line 178: Line 178:
* All [[JavaScript/JScript#RxJs|observables]] returned from HttpClient methods are cold by design. Calling <code>subscribe()</code> triggers execution of the observable and causes HttpClient to compose and send the HTTP request to the server.
* All [[JavaScript/JScript#RxJs|observables]] returned from HttpClient methods are cold by design. Calling <code>subscribe()</code> triggers execution of the observable and causes HttpClient to compose and send the HTTP request to the server.
* '''Completion''' or '''Error''' are mutually exclusive.
* '''Completion''' or '''Error''' are mutually exclusive.
* resources
** https://www.techiediaries.com/angular-11-tutorial-example-rest-crud-http-get-httpclient/


===Angular CLI===
===Angular CLI===

Revision as of 19:56, 5 October 2022

Concept

Angular is a platform and framework for building single-page client applications using HTML and TypeScript. Angular is written in TypeScript. It implements core and optional functionality as a set of TypeScript libraries that you import into your apps.

[file:///C:/Uwes/owncloud/documents/Software_Development/Programming/Frameworks/Angular/Angular.drawio]

Modules

The basic building blocks are NgModules, which provide a compilation context for components and which bundles different Angular building blocks. An Angular app is defined by a set of NgModules. An app always has at least a root module conventionally named AppModule that enables bootstrapping, and typically has many more feature modules. Like JavaScript modules, NgModules can import functionality from other NgModules, and allow their own functionality to be exported and used by other NgModules. For example, to use the router service in your app, you import the Router NgModule. 

@NgModule

Components

Every Angular application has at least one component, the root (top level) component that connects a component hierarchy (component tree) with the page document object model (DOM). A component controls a patch of screen called a view. Each component defines a selector, a class that contains application data and logic (view logic), and is associated with an HTML template that defines a view to be displayed in a target environment (see @Component).

Root Component

  • see <APP_ROOT_DIR>\src\app.component.*
  • change title in app.component.ts

Own Components

A component instance has a lifecycle that starts when Angular instantiates the component class and renders the component view along with its child views. The lifecycle continues with change detection, as Angular checks to see when data-bound properties change, and updates both the view and the component instance as needed. The lifecycle ends when Angular destroys the component instance and removes its rendered template from the DOM. 

@Component({  // from angular core
  selector: '<SELECTOR>', // tag name within html
  templateUrl: '<PATH_FILENAME>', // path and filename of the corresponding template
  template: '<HTML_CODE>', // e.g. <h1>{{title}}</h1>
  styleUrls: // the styles only apply to the component
})
export class <COMPONENT_CLASS> [implements OnInit] {
  [ngOnInit() { // is called shortly after creating a component
  }]
}

In addition each component needs to be declared in a module, normally in @NgModule ... AppModule

Components use services.

Templates

The metadata for a component class associates it with a template that defines a view. A template combines ordinary HTML with Angular directives and binding markup that allow Angular to modify the HTML before rendering it for display. The metadata for a service class provides the information Angular needs to make it available to components through dependency injection (DI). 

{{<PROPERTY>}}  // data binding to property of component class
{{<OBJECT>.<PROPERTY>}}
{{todo.targetDate}} | date // pipes are date, lowercase, uppercase, ...
(<EVENT>)=<METHOD> // event binding
[(ngModel)]="<PROPERTY_NAME>" // two-way data and event binding, for piping it has to be split into [ngModel]="... | <PIPE>" and (ngModel)
<a routerLink="/todos">here</a> // router link
Directives
Template Variables

Template Variables are defined by the prefix #<NAME>. They can be referenced e.g. in the template in Typescript code e.g. 

... <button type="button" (click)="callPhone(<NAME>.value)">Call</button> ...
Template Input Variables

The let keyword declares a template input variable that you can reference within the template e.g. 

// see bookmarks.component.html
<ng-template matMenuContent let-subMenuIndex="subMenuIndex">
  <button mat-menu-item (click)="onViewMenu(subMenuIndex)">View Menu</button>
ng-template

With <ng-template> you can define template content that is only being rendered by Angular when you, whether directly or indirectly.

Standard Events
  • click
  • dblclick
  • focus
  • blur
  • submit
  • scroll
  • cut
  • copy
  • paste
  • keydown
  • keypress
  • keyup
  • mouseenter
  • mousedown
  • mouseup
  • drag
  • dragover
  • drop
Custom Events
  • sending custom events from child to parent
@Component ...
export class ... {
  @Output() public <EVENT_NAME> = new EventEmitter[<<EVENT_TYPE>>](); // from @angular/core
  ...
  <METHOD>() {
     this.<EVENT_NAME>.emit([<VARIABLE_OF_EVENT_TYPE>]);
  • catching event in parent in parent HTML file:
<<COMPONENT_SELECTOR> (<EVENT_NAME>)="<CODE>"> </<COMPONENT_SELECTOR>>
Structural Directives

Structural directives are directives which change the DOM layout by adding and removing DOM elements. They are generally are prefixed by an asterisk, *.

Build-In Directives
  • [ngClass] // to set a style via a class
  • [ngStyle] // to set inline styles
  • [(ngModel)] // to bind properties
  • [ngIf]
*ngIf='<PROPERTY_NAME>' // shows tag only if property is true
  • [ngFor]
*ngFor="let todo of todos"
  • [ngSwitch]
  • <ng-container>

Passing Data between Components

Services

Services provide specific functionality not directly related to views. Service providers can be injected into components as dependencies, making your code modular, reusable, and efficient. Modules, components and services are classes that use decorators. These decorators mark their type and provide metadata that tells Angular how to use them.

Services only live inside the scope of their providers, so in the scope of a module or a single component. They are instantiated when injected for the first time and keept alive as long as the provider exists. As services are normal classes, angulars lifecycle hooks do not apply to them.

Angular Decorators

Dependency Injection

@Injectable({
  providedIn: 'root'
})

constructur(private <PROPERTY_NAME>: <TYP>) // depency injection

Routing

In Angular, the best practice is to load and configure the router in a separate, top-level module that is dedicated to routing and imported by the root AppModule. By convention, the module class name is AppRoutingModule and it belongs in the app-routing.module.ts in the src/app folder, which contains a routing table (sequence is important!!!): 

const routes: Routes = [
  { path: , component: LoginComponent},  // app root
  { path: 'bookmarks/menus/:id', component: MenuComponent}, 
  { path: 'welcome/:name', component: WelcomeComponent}, // parameter
  { path: '**', component: ErrorComponent} // matches everything
];

and in template: 

<router-outlet></router-outlet>

and in code: 

// see bookmarks.component.ts
this.router.navigate(
  ['/menus', this.currentSubMenuObjects[subMenuIndex].uuid], // setting required parameter
  { queryParams: { mode: "edit"} } // setting query parameter
);

Route Information

To get information of the route in the target component include in the ctor: 

private route: ActivatedRoute,

and 

// by snapshot
this.uuid = this.route.snapshot.paramMap.get('uuid');   
this.mode = this.route.snapshot.queryParamMap.get('mode');
// by observer
this.id = +this.route.snapshot.params['id']; // to get parts of the 
this.route.queryParams.subscribe(params => {this.parentId = +params['parentId'];}); // to get query params

Angular Framework Modules

FormsModule

Reactive Forms
  • example see menu.component.ts and menu.component.html

HTTPModule

  • usage
import { HttpClientModule } from '@angular/common/http';
import { HttpClient } from '@angular/common/http';
import { Observable, throwError } from 'rxjs';
import { catchError, retry } from 'rxjs/operators';

Angular CLI

Angular Command Line Interface 

ng
ng help
ng version

Add

ng add

Build

ng build

creates dist folder, which can be copied directly to a web server.

E2E

ng e2e

runs and test the entire application, uses protractor. All tests are defined in folder e2e.

Generate

Component
<APP_ROOT_DIR>> ng g[enerate] c[omponent] <COMPONENT_NAME>  // leaf the Component part of the name, it will be added automatically, e.g. ng g c app-header
// e.g.
<ROOT_DIR>>ng g c features/bookmarks

generates 

/src/app/<COMPONENT_NAME>/*

and modifies app.module.ts. If COMPONENT_NAME starts with a small letter, the generated Typescript class and the NgModule declaration starts with a capital letter. 

<APP_ROOT_DIR>/src/app/<COMPONENT_DIR>>ng g c <COMPONENT_NAME> // generates new component in /src/app/<COMPONENT_DIR>/<COMPONENT_NAME>/*
<APP_ROOT_DIR>/src/app>ng g c <COMPONENT_NAME> // generates new component in /src/app/<COMPONENT_NAME>/*
Module
ng g m <MODULE_NAME>
// generates /src/app/<MODULE_NAME>/<MODULE_NAME>.modules.ts
Service
ng generate service <PATH>/<SERVICE_NAME>

generates 

/src/app/<PATH>/<SERVICE_NAME>.service.ts

Lint

ng lint

all rules are in tslint.json.

New

ng new <APP_NAME>

creates: 

\<APP_NAME>\src\index.html // which contains the <app-root> tag
\<APP_NAME>\src\app.component.ts // defines the root component class including <app-root> tag
\<APP_NAME>\src\app.component.html // defines the root component template
\<APP_NAME>\src\app-routing.modules.ts // contains all routings
\<APP_NAME>\src\styles.css
\<APP_NAME>\src\main.ts // bootstraps the root module which itself bootstraps the root component due to the bootstrap element of the @NgModule decorator
  platformBrowserDynamic().bootstrapModule(AppModule) 
\<APP_NAME>\src\app\app.module.ts  // defines the root module

Test

ng test

uses Jasmine and Karma? and performs unit tests, see app.component.spec.ts

Serve

ng serve [--open // opens a browser with http://localhost:4200] [--port <PORT>]

polls for code changes, builds it and loads it in the browser.

Files and Directories

/tsconfig.json

describes the translation from Typescript to Javascript. 

/README.md

contains documentation. 

/package.json

contains all dependencies, frameworks and tools. 

/src/polyfill.ts

manages all browser incompabilities for Javascript. 

/src/styles.css

contains all css styles for apps. 

/src/app/

contains all modules and components. 

/src/assets/

contains images 

/src/environments/

contains configurations for all environments like test, integration, qa, ... 

/src/node_modules

all packages and frameworks installed due to listing in package.json.

Style Guide

Installation

npm install -g @angular/cli
ng // Angular cli
ng version // prints version

cd C:\Uwes\typescripts\
mkdir angular // for examples and tests

Frontend Frameworks

Examples

Test1

cd C:\Uwes\typescripts\angular
ng new test1 // enforces strict type checking yes, router yes, CSS,
cd test1
ng serve
http://localhost:4200/
CTRL + C
...
ng create services/data/messageData

uweheuer Frontend

cd C:\Uwes\typescripts\angular
ng new uh-fe // strict type checking, router, CSS
cd uh-fe
ng add @angular/material // adds Angular Material, Indigo, no typography, browser animation
// test by editing app.component.html
ng g m material // generates module
// add import to app.module.ts
ng g c features/bookmarks
ng g c features/authentication
ng g c features/home
ng g c features/externals
ng g c layout/header
ng g c layout/footer
ng g c layout/sidenav
C:\Uwes\typescripts\angular\uh-fe\src\app\features\bookmarks> ng g c menu
C:\Uwes\typescripts\angular\uh-fe> ng generate service services/backend/menuData
C:\Uwes\typescripts\angular\uh-fe> ng generate service services/backend/bookmarksData
C:\Uwes\typescripts\angular\uh-fe> ng generate service services/uiState
C:\Uwes\typescripts\angular\uh-fe> npm i angular2-uuid -s

Test Layout1

cd  cd C:\Uwes\typescripts\angular
ng new layout-test1 // strict type checking, router, CSS
cd layout-test1
npm i -s @angular/flex-layout @angular/cdk // from https://github.com/angular/flex-layout
// add FlexLayoutModule to app.modules.ts


ToDos

Resources

Retrieved from "http://uweheuer.spdns.de/mediawiki_new/index.php?title=Angular&oldid=10428"