Issue #73: Signals, Change Detection, takeUntilDestroyed Operator, bindToComponentInputs, Superpowers with Directives and DI

Signals in Angular – How to Write More Reactive Code | by Deborah Kurata

An exciting new feature is coming to Angular: signals! Signals provide a new way for our code to tell our templates (and other code) that our data has changed. This improves Angular's change detection, which also improves performance, and makes our code more reactive.

Change Detection in Angular - Pt.1 View Checking | by Decoded Frontend (Dmytro Mezhenskyi)

This video is the first one in a video series that describes the Change Detection process in Angular and shows how everything works under the hood. In this video, we will focus more on the View Checking process and learn how Angular synchronizes the component views with corresponding data models (classes). I hope you will learn a lot from this video.

Superpowers with Directives and Dependency Injection: Part 5 | by Armen Vardanyan

Here we are, part 5 of our series dedicated to Angular's directives! In previous articles we have already explored various applications of directives and dependency injection. This time around we shall see how we can use directives to help components communicate on the most hard-to-reuse level - the template.

So, let's get started with today's use case.

Getting to Know the takeUntilDestroyed Operator in Angular | by Netanel Basal

Angular v16 introduces a new feature in the @angular/core/rxjs-interop entry that includes three new operators: fromSignal, fromObservable, and takeUntilDestroyed. These operators are designed to enhance the functionality of RxJS in Angular applications.

The takeUntilDestroyed operator allows developers to automatically complete an observable when the calling context (which can be a component, directive, service, or a pipe) is destroyed. This helps prevent memory leaks and ensures that resources are released properly.

Angular: The Framework of Past, Present, and Future | by Santosh Yadav

I started using Angular in 2017 when version 4 was released. And I have seen this framework growing since then. In this blog, let's see why Angular is a framework of Past, Present, and Future.

Bind Route Info to Component Inputs (New Router feature) | by Enea Jahollari

When building applications with Angular, most of the time we use the Router to render different pages for different urls.

And based on the url we also load the data based on its path parameters or query parameters.

In the latest version of Angular v16, we will get a new feature that will simplify the process of retrieving route information in the component and make it way easier.

Why I decided to switch to the inject() function in Angular | by Joshua Morony

Angular 14 gave us the ability to use the inject() function more generally in our projects, including replacing constructor based dependency injection. But is it a good idea to switch to it?