September 2017
Intermediate to advanced
450 pages
11h 24m
English
Angular already has relatively sophisticated template error messaging that does a good job of explaining the source of most template errors. However, there are sometimes when highly nested templates can return errors in Angular can be quite tricky to track down because the templates are compiled into a generated format. Angular 4's addition of source maps for generated templates will make it easier to trace template errors back to a meaningful context in your application. Here is an example of a template related router error in Angular 2:
Can't bind to 'routerLink' since it isn't a known property of 'a'. ("<ul> <li router-active> <a [ERROR ->][routerLink]="['Index']">Home</a> </li></ul>"): AppComponent@6:7 ...Read now
Unlock full access