Angular University

We will build a series of small open source libraries (about 7) of progressively increasing difficulty, and we will learn a large number of Angular advanced features in a very fun and practical way.

We will build a series of small open source libraries (about 7) of progressively increasing difficulty, and we will learn a large number of Angular advanced features in a very fun and practical way.

What Is The Best Way To Learn Advanced Angular Features ?
Technology is never created in a vacuum - there are always certain original use cases for the appearance of a framework or even a framework feature. The best way to learn technology and according to some recent research to learn anything in general, is something called "Deliberate Practice".

So the best way to learn Angular and its most advanced features is to simply take and use it to build something very concrete, like for example an application or a library -and do it in a step-by-step way.

This is of course very time-consuming to do without any help because we will have to learn everything by ourselves along the way as we build something, gluing together an endless number of blog posts, documentation and Stackoverflow answers.

Given this, here is what will do in this course: we are going to take Angular and use it to build a series of small reusable libraries. We are going to learn the advanced features of Angular in their original use cases, where they make the most sense and so are easier to learn.

What Will We Build In This Course ?
In this course we are going to start by getting familiar with the Node library ecosystem. We are going to learn how npm dependencies really work under the hood, and what are the features that have been making the NPM Node ecosystem explode with tens of thousands of packages.

We are going to learn how and why the frontend ecosystem will also soon start benefiting from those features. Then we will start building a series of libraries: Our goal is that at the end of the course combine all the libraries we have built to create a reusable real-world dynamic modal payment widget, that will allow the user to submit payments in both Stripe and Paypal.

We will split this major component into smaller libraries: As we will be introducing testing and all the ecosystem that comes with it, we will start simple by doing a Font Awesome customizable action button.

Then we will progressively increase the difficulty of each library: we will build a dynamic tab container that allows to add new tabs at runtime, a reusable dynamic modal component with customizable content, a input mask directive to help the user introduce card numbers, a payment panel with a validated form for entering card data.

All of these libraries are reusable on their own, but fit the larger picture of building a working payments modal widget that provides a great user experience.

All of these will be tested and we will introduce animations where it makes the most sense and deploy everything to npm. We will discuss testing in detail, namely what parts of the library to test, how and and why. Each library will have a small sample application.

What Will you Learn In this Course?
We will learn how to use the Angular CLI to create a AOT compatible library, how to define a library module, how to isolate the styles of a component but still make them customizable, how to design components and directives to make them easier to maintain - making them customizable while at the same time giving the components great default behavior.

We will cover all of the more advanced features of Angular, like templates, template outlets, ng-content, ng-container, style isolation and customization, AOT, global events, debugging with the CLI, @ViewChildren, @ContentChildren, Light DOM vs Shadow DOM, @HostBinding, @HostListener, dynamic components, directives, handling keyboard events, testing, animations and more (this is a non-extensive list).

But more than presenting the features in isolation, we will use them in real use cases which will make the features much easier to learn.

Course Overview
As we will building a set of Angular libraries and deploying them in NPM, we will cover first NPM and its ecosystem - meaning how does the npm dependency management system work, and how the frontend development work is likely going to experience a similar growth to the Node ecosystem.

For more videos tutorials on Angular, check the Angular University website - https://angular-university.io

Follow us:

Twitter - https://twitter.com/AngularUniv
Google+ - https://plus.google.com/u/1/113731658...
Facebook - https://www.facebook.com/angular.univ...
Category

This Playlist contains extracts of the Complete Typescript 2 Course, the table of contents is available here - https://angular-university.io/course/typescript-2-tutorial

We wouldn't be surprised if Typescript get tremendous adoption by the enterprise in the next few years, and at the same time by the web development community. But there is something really unusual about Typescript.

This might have actually happened before maybe with Ruby on Rails, but its likely unique. With Angular 2 and Typescript, we have one of those very rare situations when a framework is actually more popular than the language itself ! Angular 2 has about the double of the search volume than Typescript, and what is stranger is the Angular 2 trend curve is growing faster than Typescript as well.

So what do these trend results mean ? That many of us are finding the language so easy to use when coming from another language that we manage to get by without diving deep into Typescript. And many of us might not have realized just how amazing this language is, and see its true disruptive potential in the enterprise and beyond.

Is Typescript Mostly for Angular 2 ?
No, Typescript is not only for Angular 2, its an amazing programming language, and its latest version Typescript 2 is so feature complete when compared to many other languages, and yet so simple to use.
There is great support for both functional and object oriented programming, its all there. In this course we will also cover OO programming but the main focus is on functional programming. How do we make sense of all this huge amount of features? What are the ones that we will be using everyday, vs the ones that we will likely almost never use ? And yet the biggest feature of the language goes beyond the language itself.

What You will Learn In This Course ?
We will do a complete introduction to Typescript 2 and to its type system. We will then immediately apply these new concepts to a practical example: we will build a REST API in Node using Express and Typescript, and then we will query a Postgresql relational database using the Sequelize ORM. We will learn how to use Typescript with third party Javascript libraries and still write type safe programs. The goal is to give a theoretical introduction to the language, but then immediately drive home those concepts by applying them to everyday tasks that we will all do in our daily lives as software developers.

RxJS and Reactive Programming can sometimes be seen as hard to get into. Although RxJs is optional in many parts of the Angular API and we can usually use Promises instead, one of the items of the Angular Project Roadmap is to allow to build reactive style applications. So clearly reactive programming is a topic that is close to the framework.

What is The Best Way To Learn RxJs ?
Why is RxJs and reactive programming sometimes seen as hard to get into ? The main reason for that could be that Observables and reactive programming are presented as either a programming paradigm shift, an alternative to promises or a generalization of functions, which are approaches that don't help as much as we could think in the learning process.

We are going to take an alternative learning take for learning these concepts: a problem / solution approach. RxJs and Observables are actually a very practical and effective solution to a very common set of problems that we face all the time while building asynchronous programs like user interfaces, and that by understanding those problems we are going to also understand RxJs - because it evolved over time as a solution to many of those problems.

These are sample lessons of the Angular Ngrx Reactive Extensions Architecture Course, the complete course is available here - https://angular-university.io/course/angular2-ngrx

We are going to build step by step a chat application that reproduces the situation that the Facebook team faced with the unread messages counter. We are going to solve the problem not by using the original Flux dispatcher, instead we are going to use a derived single store RxJs-based solution: The Angular Reactive Extensions Ngrx Store.

We are going to use the Angular CLI to quickly scaffold an application, and implement the frontend of the chat application from scratch: from an empty folder - every line of code will be explained.

The backend will also be explained but we will initially get a running backend as a starting point, so that we focus on the frontend architecture and the store solution.

We are going to build the application using Reactive Programming principles and a set of libraries of the Angular Reactives Extensions (Ngrx) Ecosystem: this will include the Ngrx Store, Ngrx Effects, DB, Router integration.

We are going to cover the benefits of Immutability and OnPush change detection, its advantages and disadvantages.

For more tutorials on Angular , have a look at the courses available in the Angular Academy - https://angular-university.io

Follow us:

Twitter - https://twitter.com/AngularUniv
Google+ - https://plus.google.com/u/1/113731658724752465218
Facebook - https://www.facebook.com/angular.university

RxJS and Reactive Programming can sometimes be seen as hard to get into. Although RxJs is optional in many parts of the Angular API and we can usually use Promises instead, one of the items of the Angular Project Roadmap is to allow to build reactive style applications. So clearly reactive programming is a topic that is close to the framework.

What is The Best Way To Learn RxJs ?
Why is RxJs and reactive programming sometimes seen as hard to get into ? The main reason for that could be that Observables and reactive programming are presented as either a programming paradigm shift, an alternative to promises or a generalization of functions, which are approaches that don't help as much as we could think in the learning process.

We are going to take an alternative learning take for learning these concepts: a problem / solution approach. RxJs and Observables are actually a very practical and effective solution to a very common set of problems that we face all the time while building asynchronous programs like user interfaces, and that by understanding those problems we are going to also understand RxJs - because it evolved over time as a solution to many of those problems.