[Solved] Identify the mistake in this Angular state update:const profile = signal({name: 'Alice'}); profile.set({name: 'Bob'}); profile().name = 'Charlie'; | Angular

Angular - State Management

Identify the mistake in this Angular state update:

const profile = signal({name: 'Alice'});
profile.set({name: 'Bob'});
profile().name = 'Charlie';

ASignals cannot hold objects as values

BCalling profile.set() twice causes a runtime error

CDirectly mutating the object returned by profile() does not update the signal

DThe initial signal value must be a string, not an object

Step-by-Step Solution

Solution:

Step 1: Understand signal immutability
Signals track changes via set(), not direct mutation.
Step 2: Analyze code
profile.set({name: 'Bob'}) correctly updates the signal.
Step 3: Identify error
Directly changing profile().name = 'Charlie' mutates the object but does not notify the signal.
Final Answer:
Directly mutating the object returned by profile() does not update the signal -> Option C
Quick Check:
Always use set() to update signals [OK]

Quick Trick: Never mutate signal value directly; use set() [OK]

Common Mistakes:

Master "State Management" in Angular

9 interactive learning modes - each teaches the same concept differently

More Angular Quizzes

Identify the mistake in this Angular state update: