Reactive programming has become a central paradigm in modern frontend development, with frameworks like Angular relying heavily on observables, eve...
For further actions, you may consider blocking this person and/or reporting abuse
Easy to understand 😀, thanks for writing one 🙏
But the computed signals use computed method as in docs is it 🤔
const count: WritableSignal<number> = signal(0);
const doubleCount: Signal<number> = computed(() => count() * 2);
Using computed like this is key for creating signals that depend on other signals, allowing Angular to handle dependencies and updates automatically.
Thanks, apologies but to me I feel that this post seems to be articulated by AI ... well it is perfectly alright but hopefully after reviewed by you or any human before 🚀😊
I see small inconsistency in describing difference between derived and computed signals.
According to Angular documentation link:
We do not distinguish between these two types of signals, name derived isn't used in the documentation. More important is the difference between WritableSignals and Signals (no-writable).
Thanks for your comment! "derived signals" is a general term for signals that depend on others, and "computed signals" are Angular's specific way of creating them using the computed function.
The documentation doesn’t use the term "derived signals," but it describes the same idea. I used it to make the difference between writable (signal) and read-only (computed) signals clearer.
Hope that helps!
Great article! I don’t write angular, and haven’t done so since Angular 1.6. But, this honestly looks pretty exciting.
A little confusing at first when you normally write React. But, it seems pretty cool 🙌🏻
The step-by-step guide from basics to advanced use cases is incredibly helpful.
Great article , I’ve been using signals for awhile now and they are awesome!
You should also talk about how to use signals along with effect()
The effect function is used with signals to trigger side effects based on changes in signal values.
Thank you for the suggestion!
I’ll consider doing a second part, maybe after Angular 19 is released.
Thank you for this article. Happy coding!