Watch Angular 2 Deep Dive

Name: Angular 2 Deep Dive
Released: 2016-06-28
Cast: Mathieu Chauvinc

2016
1 Season

Angular 2 Deep Dive is a comprehensive tutorial on the Angular 2 framework, presented by Mathieu Chauvinc from Packt Publishing. This show aims to take viewers on a deep dive into the inner workings of Angular 2, covering topics from the basics of component creation to advanced topics such as routing and testing.

The show is ideal for developers who are already familiar with the basics of Angular 2 and want to gain a deeper understanding of the framework. It is also ideal for those who already have experience with AngularJS and want to make the transition to Angular 2.

Throughout the show, Mathieu covers a range of topics related to Angular 2. He begins by discussing the basics of component creation and syntax, and then moves on to more advanced topics such as services, dependency injection, and observables. Along the way, viewers will learn how to use Angular 2 to create complex, interactive web applications.

One of the key features of Angular 2 Deep Dive is the emphasis on practical examples and code. Mathieu uses real-world examples to illustrate concepts and demonstrates how to apply Angular 2 to solve common web development problems. This approach helps viewers to not only understand the theory behind Angular 2 but to also see how it can be put into practice.

Another key aspect of the show is its coverage of testing in Angular 2. Mathieu demonstrates how to use Angular 2's testing tools to create reliable, maintainable tests for web applications. This is an essential skill for any developer working with Angular 2 and is often overlooked in other tutorials.

Throughout the show, Mathieu also emphasizes best practices and common mistakes to avoid. This is particularly helpful for those who are new to Angular 2 or who may be struggling to make the transition from AngularJS.

Overall, Angular 2 Deep Dive is an excellent resource for developers who want to gain a deeper understanding of Angular 2. With its practical examples, emphasis on testing, and coverage of best practices, this show is an essential guide for anyone looking to master the Angular 2 framework.

Filter by Source

No sources available

Do you have Hulu?

What are you waiting for?

Nice! Browse Hulu with Yidio.

Ad Info - This show may not be available on Hulu

Seasons

27. The Power of Observables

June 28, 2016

When it comes to combining events, API calls, and various other asynchronous tools, everything becomes even more complicated and confused. Observables offer a cohesive interface to combine those tools, and furthermore extend it with operators to accomplish just about anything with streams.

26. Keep Your Promises

June 28, 2016

Asynchronous processes, when they combine several actions, can be complex. Promises allow handling of such flows in a very natural way, which even at times makes us forget that the flow is asynchronous.

25. Validating Plenty

June 28, 2016

Every form needs validation, be it required fields, e-mail checking or more unique requirements. We will use built-in and customer validators to evaluate a form's validity and to display the corresponding errors.

24. When the Model Gets Involved

June 28, 2016

Template-based forms can quickly get cluttered and its declarativity soon becomes a lack of separation of concerns. Using NgFormModel, we can ensure that more complex and future proof forms are built.

23. Go Full Template

June 28, 2016

Almost every site or app contains at least one form. Sometimes, forms can be simple and we want a quick way to implement them while still making use of validation and error display. We will build a fully template-based form that is quick, yet powerful.

22. Asynchronous Piping

June 28, 2016

Many components simply load data asynchronously and then set the given data onto the template. The async pipe offers to deal with such a case, as well as to guarantee that on destroy, the corresponding listeners will be stopped, thus avoiding memory leaks.

21. Stay Pure

June 28, 2016

One of the promises of Angular 2 is to be more efficient and faster. When confronted with mutable objects, Angular assumes they may have been modified; except within pipes. Let's consider ways to deal with that exception, good and bad.

20. Custom Pipes

June 28, 2016

Existing pipes in Angular 2 cover a fair amount of use cases of pipes. But not all. We create our own pipe and extend it to use parameters.

19. Built-in Pipes

June 28, 2016

Separating concerns between view logic and presentation is vital. However, it is also helpful to use a declarative way to apply simple modifications on data from within the template. To achieve this, we will use pipes that are built into Angular 2.

18. Lifecycle Hooks

June 28, 2016

At various, important moments in an application, we might want to interject and conduct some actions. Hooks provide a way to do so in a very pluggable manner.

17. Child Routing

June 28, 2016

Under a single item page, it is common to have sub-items, for example, the details for a track, and the artist for a track. We can handle all routes from the main component, but that's messy and not very future proof. With the new router's child routing abilities, we will extend a single item route defined at the top level, with sub-routes defined on the single track page component.

16. Routing with Parameters

June 28, 2016

Pages that display a single item, for example, an article or a track, need to read their ID from the URL of the route. We will create a route that includes such a parameter and capture it from the target component.

15. Configuring the Router and Displaying Components

June 28, 2016

Sites rarely have a single page; we need to be able to navigate from one page to another. We'll use Angular's router to enable such navigation.

14. Testing a Service

June 28, 2016

Tests are great to ensure quality of work, avoid breaking changes and in general make developers feel comfortable about the code they write. We'll use a typical testing setting to unit-test an ES6 class and the service we built earlier.

13. Hierarchy of Injectors

June 28, 2016

It is rare for all components in an application to want to use a service in the same manner. There will always be small customizations needed, even within the same application. The hierarchy of injectors makes it possible to handle those intricacies while remaining Don't Repeat Yourself principle (DRY).

12. The Power of Providers

June 28, 2016

The strength of dependency injection is that a constructor does not need to know what implementation of each of its dependencies it uses. Using "provide," we can override a service and make full use of the strengths of dependency injection.

11. Creating an Injectable

June 28, 2016

Logic should not be kept inside a component. So we'll build our own service to take care of the loading of data and mapping to track objects.

10. Built-in Services

June 28, 2016

The business layer needs to be separated from the presentation layer. Also data is often pulled from a server. We'll make use of built-in injectables and in particular the HTTP service to achieve those two goals.

9. Directives

June 28, 2016

Some components don't expect to display anything. They need to act on the existing element they are added to. These are called directives in Angular 2 and are basically components without a view. We'll create one.

8. Content Projection

June 28, 2016

Sometimes, the markup coded in a template needs to be kept in the template of a smaller component. This is called content projection, and we'll use ng-content to achieve that.

7. I/O - Component Data and Event Emitters

June 28, 2016

As we add more specific, reusable components, they will need to communicate with one another. We'll use @Input and @Output to communicate to and from parent and child components.

6. Creating Your Own Component

June 28, 2016

Cluttering our entire app into a single root component will not be scalable, nor allow us to reuse components. So we'll create our own component to handle a smaller part of the application.

5. Binding to Events

June 28, 2016

We need to react to the user's interactions such as clicking and typing. For this, we'll bind to events.

4. One-way Data Binding

June 28, 2016

We want to display data from the JavaScript side onto the screen. This is done via data binding from the component to the template.

3. To TypeScript or Not to TypeScript, That Is No Question

June 28, 2016

Is it worth it to use TypeScript for Angular 2 projects? We think it is, and we'll show why in this video.

2. The Root of All Things

June 28, 2016

We need to get started with our project. For this, we'll use a seed project and install all dependencies so that a simple gulp task allows us to run our app.