{"id":931,"date":"2023-05-10T05:00:00","date_gmt":"2023-05-10T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=931"},"modified":"2023-05-09T14:53:29","modified_gmt":"2023-05-09T21:53:29","slug":"signals-why-and-when-do-we-need-them","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/signals-why-and-when-do-we-need-them\/","title":{"rendered":"Signals: Why and when do we need them?"},"content":{"rendered":"\n

With the release of Angular 16<\/a>, Signals are now available as a developer preview, which means we can start learning about Signals<\/a>, testing them, and possibly adopting them.<\/p>\n\n\n\n

The end goal of Signals is simple: Improve change detection<\/a> in the Angular framework<\/strong> by removing the need for Zone.js. A signal-based application will be able to update individual views (a view is a sub-set of a component template \u2014 we create new views every time we use structural directives such as ngIf<\/code> or ngFor<\/code>) one by one instead of checking the entire component tree, enabling laser-focused updates of our DOM<\/strong>.<\/p>\n\n\n\n

A secondary goal is to make Angular easier to learn<\/strong> by making RxJs less critical than before, which also applies to state management libraries such as NgRx or NgXs. In other words, we can rely less on operators, subjects<\/a>, and the like.<\/p>\n\n\n\n

Now that we covered the why<\/strong>, let’s talk about when to use signals<\/strong>. To get the full benefit of Signals in the long run, using them everywhere we have Observables or data bindings makes sense. I know this sounds like a lot of work, but that’s how we can get to a point where Angular can tell exactly which components must be updated when a value changes<\/strong>, no matter their location in the DOM tree.<\/p>\n\n\n\n

An upcoming feature of Angular (v17 or later) will be signal-based components<\/a>, where inputs, outputs, and even two-way bindings will be expressed as Signals:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

I believe it makes sense to start using Signals as soon as possible. The base API is available in Angular 16 and is easy to learn. I already published a course that will be continuously updated as Signals evolve<\/a>.<\/p>\n\n\n\n

If you have any specific questions or concerns, feel free to send me your questions. I’ll be covering more about Signals as part of this newsletter.<\/p>\n","protected":false},"excerpt":{"rendered":"

With the release of Angular 16, Signals are now available as a developer preview, which means we can start learning about Signals, testing them, and possibly adopting them. The end goal of Signals is simple: Improve change detection in the Angular framework by removing the need for Zone.js. A signal-based application will be able to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,29],"tags":[],"class_list":["post-931","post","type-post","status-publish","format-standard","hentry","category-angular","category-signals"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t