{"id":6979,"date":"2023-03-02T04:36:01","date_gmt":"2023-03-02T03:36:01","guid":{"rendered":"https:\/\/www.angulararchitects.io\/?p=6979"},"modified":"2025-06-05T09:47:19","modified_gmt":"2025-06-05T07:47:19","slug":"angular-signals","status":"publish","type":"post","link":"https:\/\/www.angulararchitects.io\/en\/blog\/angular-signals\/","title":{"rendered":"Signals in Angular: Building Blocks"},"content":{"rendered":"
\n\t\t\t\n\t\n\t\n\t\t

\n\t\t\tThis is post 1 of 9 in the series “Signals”<\/em>\t\t<\/p>\n\t\t\t<\/label>\n\n\t\t\t

\n\t\t\t
    \n\t\t\t\t\t\t\t\t\t
  1. Signals in Angular: Building Blocks<\/span><\/li>\n\t\t\t\t\t\t\t\t\t
  2. Component Communication with Signals: Inputs, Two-Way Bindings, and Content\/ View Queries<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  3. Successful with Signals in Angular – 3 Effective Rules for Your Architecture<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  4. Skillfully Using Signals in Angular – Selected Hints for Professional Use<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  5. When (Not) to use Effects in Angular — and what to do instead<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  6. Asynchronous Data Flow with Angular’s new Resource API<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  7. Streaming Resources in Angular – Details and Semantics<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  8. Streaming Resources for a Chat with Web Sockets: Messages in a Glitch-Free World<\/a><\/li>\n\t\t\t\t\t\t\t\t\t
  9. Angular’s new httpResource<\/a><\/li>\n\t\t\t\t\t\t\t<\/ol>\n\t\t<\/div>\n\t<\/div>\n

    With the introduction of Signals, Angular provides a new reactive building block that makes state management significantly simpler. Its lightweight and accessible API is ideal for developers who want a straightforward way into reactive programming. Many common use cases can now be implemented with minimal code.<\/p>\n

    RxJS remains the powerful solution for advanced scenarios like streams, cancelation, and complex data flow. The good news: Signals and RxJS integrate seamlessly. This interoperability allows developers to combine simplicity and flexibility as needed.<\/p>\n

    Signals also work hand in hand with Angular\u2019s OnPush change detection strategy and are designed to support the upcoming zone-less change detection. In fact, they may serve as the foundation for even more fine-grained change detection mechanisms in the future.<\/p>\n

    This article series explores how to use Angular Signals effectively\u2014from the basics to advanced patterns. This first part covers the foundational building blocks:
    \nsignal<\/code>, computed<\/code>, effect<\/code>, and untracked<\/code>.<\/p>\n

    \ud83d\udcc2 Source Code<\/a> (see branches<\/strong> signal<\/code> and signal-rxjs-interop<\/code>)<\/p>\n

    Using Signals<\/h2>\n

    For using Signals with data binding, properties to be bound are expressed as signals:<\/p>\n

    @Component([\u2026])\nexport class FlightSearchComponent {\n\n  private flightService = inject(FlightService);\n\n  from = signal('Hamburg');\n  to = signal('Graz');\n  flights = signal<Flight[]>([]);\n\n  [\u2026]\n\n}<\/code><\/pre>\n
    It should be noted here that a Signal always has a value. Therefore, a default value must be passed to the signal<\/code> function. If the data type cannot be derived from this, the example specifies it explicitly via a type parameter.<\/p>\n
    The Signal's getter is used to read the value of a signal. Technically, this means that the signal is called like a function:<\/p>\n
    async search(): Promise<void> {\n  if (!this.from() || !this.to()) {\n    return;\n  }\n  const flights = await this.flightService.findAsPromise(this.from(), this.to());\n  this.flights.set(flights);\n}<\/code><\/pre>\n
    To set the value, the signal offers an explicit setter in the form of a set<\/code> method. The example shown uses the setter to stow the loaded flights. The getter is also used for data binding in the template:<\/p>\n
    <div *ngIf="flights().length > 0">\n  {{flights().length}} flights found!\n<\/div>\n\n<div class="row">\n  <div *ngFor="let f of flights()">\n    <flight-card [item]="f" \/>\n  <\/div>\n<\/div><\/code><\/pre>\n
    Method calls were frowned upon in templates in the past, especially since they could lead to performance bottlenecks. However, this does not generally apply to uncomplex routines such as getters. In addition, the template will appear here as a consumer, and as such, it can be notified of changes.<\/p>\n
    Meanwhile, Angular's Two-Way-Bindings directly support Signals:<\/p>\n
    <form #form="ngForm">\n  <div class="form-group">\n    <label>From:<\/label>\n    <input [(ngModel)]="from" name="from" class="form-control">\n  <\/div>\n\n  <div class="form-group">\n    <label>To:<\/label>\n    <input [(ngModel)]="to" name="to" class="form-control">\n  <\/div>\n\n  <div class="form-group">\n    <button class="btn btn-default" (click)="search()">Search<\/button>\n    <button class="btn btn-default" (click)="delay()">Delay<\/button>\n  <\/div>\n<\/form><\/code><\/pre>\n
    In a future version, the Angular team will adopt the forms handling to Signals.<\/p>\n
    Updating Signals<\/h2>\n
    In addition to the setter shown earlier, Signals also provide an update<\/code> method for projecting the current value to a new one:<\/p>\n
    this.flights.update(f => {\n  const flight = f[0];\n  const date = addMinutes(flight.date, 15);\n  const updated = {...flight, date};\n\n  return [\n    updated,\n    ...f.slice(1)\n  ];\n});<\/code><\/pre>\n
    Signal Values Should to be Immutable<\/h2>\n
    By default, a Signal's is supposed to be immutable. For this reason, just updating the flight date in the previous section would not be sufficient. Instead, we have to clone the changed parts, so that they get a new object reference. <\/p>\n
    By comparing these references, Angular's OnPush<\/code> change detection strategy can efficiently determine the changed parts of an object managed by a Signal. In the previous section, the Array and the first flight get an new object reference. The other flights are not changed and hence just copied over using slice<\/code>. As a result, they keep their object reference. <\/p>\n
    Calculated Values, Side Effects, and Assertions<\/h2>\n
    Some values are derived from existing values. Angular provides calculated signals for this:<\/p>\n
    flightRoute = computed(() => this.from() + ' to ' + this.to());<\/code><\/pre>\n
    Such a signal is read-only and appears as both a consumer and a producer. As a consumer, it retrieves the values of the signals used - here from<\/code> and to<\/code> - and is informed about changes. As a producer, it returns a calculated.<\/p>\n
    If you want to consume signals programmatically, you can use the effect<\/code> function:<\/p>\n
    constructor() {\n    effect(() => {\n        console.log('from:', this.from());\n        console.log('route:', this.flightRoute());\n    });\n}<\/code><\/pre>\n
    The effect<\/code> function executes the transferred lambda expression and registers itself as a consumer for the signals used. When one of these signals change, the the effect is triggered again.<\/p>\n
    Please note that usually, Signals are consumed via data binding. However, in some cases, we need a function or method call in order to present a Signal's value to the user. Examples are logging or displaying a toast message. Please find more details on the ideas behind effects here<\/a>.<\/p>\n
    Injection Context needed<\/h2>\n
    Several building blocks for Signals such as effect<\/code> can only be used in an injection context. This is everywhere inject<\/code> is allowed: in the constructor, as default values of class fields, and in provider factories. Also, you can use the runInInjectionContext<\/code> function to run code in an injection context.<\/p>\n
    Hence, the effect set up in the constructor above would fail when placed in ngOnInit<\/code> or in another method:<\/p>\n
    ngOnInit(): void {\n    \/\/ Effects are not allowed here.\n    \/\/ Hence, this will fail:\n    effect(() => {\n        console.log('route:', this.flightRoute());\n    });\n}<\/code><\/pre>\n
    In this case, you'd get the following error:<\/p>\n
    \n
    ERROR Error: NG0203: effect() can only be used within an injection context such as a constructor, a factory function,<\/p>\n<\/blockquote>\n
    The technical reason is that effects use inject<\/code> to get hold of the current DestroyRef<\/code>. This service provided since Angular 16 helps to find out about the life span of the current building block, e. g. the current component or service. The effect uses the DestroyRef<\/code> to "unsubscribe" itself when this building block is about to be destroyed.<\/p>\n
    For this reason, you would typically setup your effects in the constructor as shown in the last section. If you really want to setup an effect somewhere else, you can go with the runInInjectionContext<\/code> function. However, it needs a reference to an Injector<\/code>:<\/p>\n
    injector = inject(Injector);\n\nngOnInit(): void {\n  runInInjectionContext(this.injector, () => {\n    effect(() => {\n      console.log('route:', this.flightRoute());\n    });\n  });\n}<\/code><\/pre>\n
    Glitch-Free Property<\/h2>\n
    If a signal changes several times in a row or if several signals change one after the other, undesired interim results could occur. Let's imagine we change the search filter Hamburg - Graz<\/code> to London - Paris<\/code>:<\/p>\n
    setTimeout(() => {\n  this.from.set('London');\n  this.to.set('Paris');\n}, 2000);<\/code><\/pre>\n
    Here, London - Graz<\/code> could come immediately after the setting from<\/code> to London<\/code>. Like many other Signal implementations, Angular's implementation prevents such occurrences. The Angular team's readme<\/a>, which also explains the push\/pull algorithm used, calls this desirable assurance "glitch-free".<\/p>\n
    Signals and Change Detection<\/h2>\n
    Similar to an Observable bound to a template using the async<\/code>-Pipe, a bound Signal triggers change detection. This also works for the more efficient OnPush<\/code> mode:<\/p>\n
    @Component({\n  [...]\n  changeDetection: ChangeDetectionStrategy.OnPush\n})\nexport class FlightSearchComponent { [...] } \n\n[...]\n\n@Component({\n  [...]\n  changeDetection: ChangeDetectionStrategy.OnPush\n})\nexport class FlightCardComponent { [...] } <\/code><\/pre>\n
    However, to help Angular in OnPush<\/code> mode to also find out about child components to look at, you have to use Immutables, as discussed above.<\/p>\n
    RxJS Interop<\/h2>\n
    Admittedly, at first glance, signals are very similar to a mechanism that Angular has been using for a long time, namely RxJS Observables. However, signals are deliberately kept simpler. <\/p>\n
    If you need the power of RxJS and its operators, you can however convert them to Observables. The namespace @angular\/core\/rxjs-interop<\/code> contains a function toObservable<\/code> converting a Signal into an Observable and a function toSignal<\/code> for the other way round. They allow using the simplicity of signals with the power of RxJS.<\/p>\n
    The following listing illustrates the use of these two methods by expanding the example shown into a debounced type-ahead:<\/p>\n
    @Component([...])\nexport class FlightSearchComponent {\n  private flightService = inject(FlightService);\n\n  from = signal('Hamburg');\n  to = signal('Graz');\n  basket = signal<Record<number, boolean>>({ 1: true });\n  flightRoute = computed(() => this.from() + ' to ' + this.to());\n\n  from$ = toObservable(this.from);\n  to$ = toObservable(this.to);\n\n  flights$ = combineLatest({ from: this.from$, to: this.to$ }).pipe(\n    filter(c => c.from.length >= 3 && c.to.length >= 3),\n    debounceTime(300),\n    switchMap(c => this.flightService.find(c.from, c.to))\n  );\n\n  flights = toSignal(this.flights$, {\n    initialValue: []\n  });\n}<\/code><\/pre>\n
    The example converts the signals from<\/code> and to<\/code> into the observables from$<\/code> and to$<\/code> and combines them with combineLatest<\/code>. As soon as one of the values changes, filtering and debouncing occur before switchMap<\/code> triggers the backend request. One of the benefits flattening operators like switchMap<\/code> come with are guarantees in terms of asynchronicity. These guarantees help to avoid race conditions.<\/p>\n
    The initialValue<\/code> passed to toSignal is needed because Signals always have a value. On the contrary, Observables might not emit a value at all. If you are sure your Observable has an initial value, e.g., because it's a BehaviorSubject<\/code> or because of using the startsWith<\/code> operator, you can also set requireSync<\/code> to true<\/code>:<\/p>\n
    flights = toSignal(this.flights, { \n    requireSync: true\n});<\/code><\/pre>\n
    If you neither set initialValue<\/code> nor requireSync<\/code>, the type of the returned Signal also supports the undefinied<\/code> type, allowing an initial value of undefined<\/code>. In the example shown, this would result in a Signal<Flight[] | undefinied><\/code> instead of Signal<Flight[]><\/code>. Consequently, your code has to check for undefined<\/code> too.<\/p>\n
    Conclusion<\/h2>\n
    Signals make reactivity in Angular more lightweight. They make usual use cases simple and for more complex use cases we can bridge over to RxJS using a first-class interop implementation.<\/p>\n
    The Angular team remains true to itself: Signals are not hidden in the substructure or behind proxies but made explicit. Developers therefore always know which data structure they are actually dealing with. Also, signals are just an option. No one needs to change legacy code and a combination of traditional change detection and signal-based change detection will be possible.<\/p>\n
    More on Modern Angular?<\/h2>\n
    Learn all about Standalone Components in our free eBook:<\/p>\n