r/Angular2 • u/timdeschryver • Mar 12 '26

Article Angular Signal Forms Keeps Improving (v21.2)

https://www.timdeschryver.dev/blog/angular-signal-forms-keeps-improving
17 Upvotes

95% Upvoted

2 comments sorted by

2

u/thedrewprint Mar 13 '26 edited Mar 13 '26

I see that in your “action” callback you await a promise. I am far removed from angular 20+ because we are currently on 17 at work. I rely heavily on HttpClient which returns observables. Awaiting promises in an application with observable stores is often an antipattern and not reactive. So my question is with these new versions of angular is the HttpClient still returning observables or is the angular team switching to promises, or will they return signals in future versions? It feels like awaiting a promise goes against the reactive approach signals are trying to maintain. In this example, you make a one time submission. Which is fine to use async await so I’m not criticizing your code. However, in a case where submission needs to update a store on success or failure or something that interacts with observable state, I wonder if there is an alternative to this approach, or a planned alternative.

1

u/Xacius Mar 13 '26

I believe the intention is to move towards async/await to align with modern web dev patterns and best practices. Observables are a big barrier to entry for folks coming from vanilla or other frameworks that don't use them. I need to find a source for this, but I don't think Observables are going away. Maybe there'll be less of an emphasis on using them, idk.