Signal-based components help your app update the screen automatically when data changes. They make your code simpler and faster.
Signal-based components in Angular
import { Component, signal } from '@angular/core'; @Component({ selector: 'app-counter', standalone: true, template: ` <button (click)="increment()">Increment</button> <p>Count: {{ count() }}</p> ` }) export class CounterComponent { count = signal(0); increment() { this.count.update(c => c + 1); } }
The signal() function creates a reactive value that Angular tracks.
Use count() to read the current value inside the template or code.
count(), and set a new value with count.set().count = signal(10); // Read value console.log(count()); // Update value count.set(20);
update() to change the value based on the old value.count = signal(0); increment() { this.count.update(c => c + 1); }
message = signal('Hello'); changeMessage() { this.message.set('Hi there!'); }
This component shows a button and a count. Each click increases the count automatically on screen.
import { Component, signal } from '@angular/core'; @Component({ selector: 'app-click-counter', standalone: true, template: ` <button (click)="increment()" aria-label="Increment count">Click me</button> <p>You clicked {{ count() }} times.</p> ` }) export class ClickCounterComponent { count = signal(0); increment() { this.count.update(c => c + 1); } }
Signals automatically update the UI when their value changes, no extra code needed.
Use signal() only inside components or services where you want reactive data.
Remember to use count() to read the signal value, not count directly.
Signals hold reactive data that updates the UI automatically.
Use signal() to create reactive values and update() or set() to change them.
Signal-based components make your Angular apps simpler and faster.
Practice
signal() in Angular signal-based components?Solution
Step 1: Understand what
signal()doessignal()creates a reactive value that Angular tracks for changes.Step 2: Connect
When the signal value changes, Angular automatically updates the UI without manual intervention.signal()to UI updatesFinal Answer:
To create reactive data that updates the UI automatically -> Option DQuick Check:
signal() creates reactive data = D [OK]
- Confusing signal() with module or HTTP functions
- Thinking signal() handles styling
- Assuming signal() is for event handling
count in Angular?Solution
Step 1: Recall the signal update method
Signals have aset()method to assign a new value.Step 2: Check the syntax for updating
The correct syntax iscountcount.set(5);to update the signal value.Final Answer:
count.set(5); -> Option CQuick Check:
Use set() method to update signals = A [OK]
- Trying to assign directly like a normal variable
- Using update() instead of set() incorrectly
- Calling set() as a standalone function
const count = signal(0); count.set(count() + 1); console.log(count());
What will be printed in the console?
Solution
Step 1: Understand initial signal value
The signalcountstarts at 0.Step 2: Evaluate the update expression
count.set(count() + 1);reads current value 0, adds 1, sets new value 1.Step 3: Check the console output
console.log(count());prints the updated value 1.Final Answer:
1 -> Option AQuick Check:
Initial 0 + 1 = 1 printed = B [OK]
- Forgetting to call count() to get value
- Expecting 0 because of no visible loop
- Confusing set() with update()
const name = signal('Alice');
name.update('Bob');Solution
Step 1: Check usage of update() method
update()expects a function to modify the current value, not a direct value.Step 2: Identify the incorrect argument
Passing 'Bob' directly causes an error; it should bename.update(value => 'Bob')or useset().Final Answer:
Using update() with a direct value instead of a function -> Option BQuick Check:
update() needs a function argument = C [OK]
- Passing direct value to update() instead of a function
- Confusing update() and set() usage
- Thinking signals can't hold strings
"Learn Signals"?Solution
Step 1: Understand signal holding an array
The signaltasksholds an array, accessed by callingtasks().Step 2: Correctly add a new task immutably
Use spread syntax to create a new array with existing tasks plus the new one, then set it withtasks.set().Step 3: Identify incorrect options
Options B and D misusepush()which returns length, not array; C assigns directly, breaking reactivity.Final Answer:
tasks.set([...tasks(), 'Learn Signals']); -> Option AQuick Check:
Use set() with new array copy = A [OK]
- Using push() inside update() or set() incorrectly
- Assigning directly to signal variable
- Not creating a new array copy for immutability
Ready to prove it?
Pass the test and this pattern moves unknown
