Book Image

TypeScript 2.x By Example

By : Sachin Ohri
Book Image

TypeScript 2.x By Example

By: Sachin Ohri

Overview of this book

The TypeScript language, compiler, and open source development toolset brings JavaScript development up to the enterprise level. It allows you to use ES5, ES6, and ES7 JavaScript language features today, including classes, interfaces, generics, modules, and more. Its simple typing syntax enables building large, robust applications using object-oriented techniques and industry-standard design principles. This book aims at teaching you how to get up and running with TypeScript development in the most practical way possible. Taking you through two exciting projects built from scratch, you will learn the basics of TypeScript, before progressing to functions, generics, promises, and callbacks. Then, you’ll get to implement object-oriented programming as well as optimize your applications with effective memory management. You’ll also learn to test and secure your applications, before deploying them. Starting with a basic SPA built using Angular, you will progress on to building, maybe, a Chat application or a cool application. You’ll also learn how to use NativeScript to build a cool mobile application. Each of these applications with be explained in detail, allowing you to grasp the concepts fast. By the end of this book, you will have not only built two amazing projects but you will also have the skills necessary to take your development to the next level.
Table of Contents (11 chapters)

Understanding dependency injection in Angular

Dependency injection is one of the most fundamental aspects of Angular. The Angular team has been very careful in using dependency injection since its first release of the Angular 1.x version and this has been the primary reason that Angular applications are easy to test.

The ability to write good, robust tests for an application largely depends on how the application manages dependencies. If the application creates concrete dependencies in its classes than it becomes very difficult to write test cases for individual classes, whereas if the dependencies are not the primary responsibility of a class, then writing test cases for that class becomes so much simpler.

We have been implicitly relying on dependency injection since our first application, and some of the code examples in our Trello application where we use Angular's dependency...