Book Image

TypeScript Blueprints

By : Ivo Gabe de Wolff
Book Image

TypeScript Blueprints

By: Ivo Gabe de Wolff

Overview of this book

TypeScript is the future of JavaScript. Having been designed for the development of large applications, it is now being widely incorporated in cutting-edge projects such as Angular 2. Adopting TypeScript results in more robust software - software that is more scalable and performant. It's scale and performance that lies at the heart of every project that features in this book. The lessons learned throughout this book will arm you with everything you need to build some truly amazing projects. You'll build a complete single page app with Angular 2, create a neat mobile app using NativeScript, and even build a Pac Man game with TypeScript. As if fun wasn't enough, you'll also find out how to migrate your legacy codebase from JavaScript to TypeScript. This book isn't just for developers who want to learn - it's for developers who want to develop. So dive in and get started on these TypeScript projects.
Table of Contents (16 chapters)
TypeScript Blueprints
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Advantages of Flux


In this section you can find some of the advantages of using Flux, the architecture that we used in this chapter.

Flux is based on the unidirectional flow of data. Angular supports two way bindings, which allow data to flow in two directions. With this data flow, a lot of properties might get changed after a single change is made. This can lead to unpredictable behavior in big applications. Flow and React do not have such bindings, but instead there is a clean flow of data (store | view | action | dispatch | store).

The parts of Flux are not strictly bound to each other. This makes it easy to test specific parts of the application with unit tests. We already saw that the actions do not depend on the view.

Going cross-platform

Since the parts of Flux are not bound, we can, relatively, replace the HTML views of the application with views of a different platform. The user interface does not store the state of the application, but it is managed in the store. The other parts need...