Angular 2. Useful links. Allen Holub 2-1

Transcription

1 Angular 2 Allen Holub Useful links 2-1 2

2 Useful links Useful links

3 Useful links Useful links

4 Useful links Quickstart Seed git clone quickstart cd quickstart npm install npm start Module Architecture 3 3-1

5 Module Architecture Template (html) { data/methods (typescript) metadata (in module) Module Architecture Service Service Service { Template (html) data/methods (typescript) metadata (in module) 3-3 3

6 {{value}} Bindings DOM [property] = "value" (event) = "handler" [(ng-model)] = "property" <li>{{hero.name}}</li> <hero-detail [hero]="selectedhero"></hero-detail> <li (click)="selecthero(hero)"></li> 4 4 Directives *ngfor=" " *ngif <li *ngfor="let hero of heroes"></li> <hero-detail *ngif="selectedhero"></hero-detail> 5 5

7 Dependency Injection Services (are essentially just classes) Form support Lifecycle hooks Router Testing (Angular Testing Platform) Other Stuff 6 6 The good 7 7-1

8 Bindings are way cool The fact that everything updates automatically saves a lot of dev time. The good Bindings are way cool The fact that everything updates automatically saves a lot of dev time. Easier than Javascript/JQuery Might be a plus if you're dealing with undisciplined programmers The good 7 7-3

9 Bindings are way cool The fact that everything updates automatically saves a lot of dev time. Easier than Javascript/JQuery Might be a plus if you're dealing with undisciplined programmers Architecture is well understood Can't use normal html-development tools Bugs are hard to find The good Bindings are way cool The fact that everything updates automatically saves a lot of dev time. Easier than Javascript/JQuery Might be a plus if you're dealing with undisciplined programmers Architecture is well understood Can't use normal html-development tools Bugs are hard to find s are uniform Well defined structure and lifecycle The good 7 7-5

10 The bad and the ugly It's an Angular app Angular owns your entire page Forces a data-object architecture on you No design flexibility, polyglot implementation, etc. Not great for μservices Write only Apps get complex and hard to read very quickly Definitions are spread all over the place The bad and the ugly 8-2 8

11 It's an Angular app Angular owns your entire page Forces a data-object architecture on you No design flexibility, polyglot implementation, etc. Not great for μservices Write only Apps get complex and hard to read very quickly Presentation Definitions are spread all over the place (javascript/html) The bad and the ugly Agent Abstraction (Microservice) Presentation Abstraction Control It's an Angular app Angular owns your entire page Forces a data-object architecture on you No design flexibility, polyglot implementation, etc. Not great for μservices Write only Apps get complex and hard to read very quickly Definitions are spread all over the place The bad and the ugly 8-4 8

12 It's an Angular app Angular owns your entire page Forces a data-object architecture on you No design flexibility, polyglot implementation, etc. Not great for μservices Write only Apps get complex and hard to read very quickly Definitions are spread all over the place Uses strings for html Can't use normal html-development tools The bad and the ugly html bugs are hard to find Directives are too limiting Debugging is Painful (mysterious runtime errors) code() 9

13 Allen Holub 10