Original cover photo by Shyam on Unsplash.
If we ask any Angular developer "What is the hottest topic in Angular right now?", with almost 100% cer...
For further actions, you may consider blocking this person and/or reporting abuse
Very informative, I have been guilty of using "allowSignalWrites" in effects, at least I updated signals :) .. but I love the patterns you showed here.
As a side note, I just ported one of our internal applications to use signal inputs(), and it's so awesome. The best thing? ngOnChanges are now no more needed, effect() and computed() to the rescue. Awesome.
NgOnChanges is really horrible to work with
Yes, signal inputs are clearly a superior approach! Totally agree. Thanks for appreciating the article :)
Thanks for sharing!
Informative Post well done keep it up
Regard
Danish Hafeez | QA Assistant
ictinnovations.com
Thanks for your appreciation!
Good article. Thanks.
Have recently upgraded to the latest Angular. Very excited to start working with Signal inputs!
Great to hear I have been of help to you!
Thank you for sharing.
Thank you for this amazing article, @armandotrue 👏
The toObservable-toSignal composition is elegant and it's the first time I've seen it.
However, doesn't this make the HTTP request side effect eager unless we use RxJS operators to guard against this? One thing you forgot is initializing the
query
signal with empty string (''
) or another bottom value. The thing about signals is that they, likeBehaviorSubject
s alway must have a current value, causing theitems
signal and its built-in effect to immediately (well, after 500ms) kick off.Do you have tips on the
allowSignalWrites
effect option, @armandotrue?Hi Armen Vardanyan,
Excellent content, very useful.
Thanks for sharing.
Good article. Thanks))
Thank you for sharing, Armen! Really useful.
Question about companyEmployees. How it will get updated if a company value is updated with selector for example and it is untracked?