Thank you for watching the video! Http calls are not necessarily unavoidable. You can use fetch instead of HTTP Client to retrieve data using promises. Personally, I prefer HTTP Client (which as you said returns an observable). Using signals won't necessarily replace all Observables, especially when dealing with event-based actions. Things like tracking/reacting to keypresses, when you want every emitted value, you'll still want Observables. So yes, signals will replace many observables, especially those used to manage state. But we'll still want observables for event-based actions.

For simple applications, yes. For more complex applications and for large teams, probably no. And ngRx, and of course signalStore, are becoming more signal based.

In some cases, yes. Especially those cases where combineLatest was used to handle multiple query parameters. In other cases, there may still be use for combineLatest, such as when handling events from multiple sources (keypress and mouse move for example).

That is so very kind of you to say! I appreciate that! 😊

Thank you so very much! 😊 Thanks for watching!

Thanks!

Thank you so much! All the best in 2025! 😊

Great tooling for the win! LOL. Glad it was useful. 😊

I'm glad you found it helpful! 😊

Thank you! I'm really glad you enjoyed it! 😊

Thanks! Do you have a code snippet of your combineLatest so I have a clear idea of your objective? I used to use combineLatest to do something with a retained observable when another observable changes. If these are all signals instead, the linkedSignal() can often do the same job. It depends on your specific scenario.

@@deborah_kurata I meant that if I can use Resource or RxResource to handle multiple http request. It seems that it can only handle one request with loader function in Resource or RxResource. To handle multiple request, it seems that we still can not avoid to use combineLatest. I asked Grok AI. It gave me the answer. `import { inject, Injectable } from '@angular/core'; import { resource } from '@angular/core'; import { HttpClient } from '@angular/common/http'; @Injectable({ providedIn: 'root' }) export class MultiResourceService { private http = inject(HttpClient); combinedResource = resource({ loader: async () => { const [users, products] = await Promise.all([ this.http.get<User[]>('url1').toPromise(), this.http.get<Product[]>('url2').toPromise() ]); return { users, products }; } }); }` or another way `private http = inject(HttpClient); usersResource = rxResource({ loader: () => this.http.get<User[]>('url1') }); productsResource = rxResource({ loader: () => this.http.get<Product[]>('url2') }); combinedResource = combineLatest([this.usersResource.result$, this.productsResource.result$]).pipe( map(([users, products]) => ({ users, products })) ); combinedResource.subscribe(result => { console.log(result.users, result.products); });`

Yep! Signals are fun! Thanks

Thank you so much! All the best for 2025! 😊

Yep! Model inputs are so useful, it's been difficult finding a scenario for using an Output anymore. Thanks!

We'd still use HTTPClient (or fetch), so that would be the same. We just wouldn't need to return the result as a signal, so it wouldn't need to be wrapped in a resource.

Thank you! Happy New Year!

Thank you! All the best for 2025! 😊

Thank you! All the best for 2025! 😊

I'm glad you found it helpful! 😊 Thanks for watching!

Thanks, I appreciate it! 😊 Happy New Year!

Thanks! As someone that taught Angular for many years, I saw numerous new Angular developers really struggle with ngModules. Conceptually, standalone is easier to understand. Your component needs two-way binding, import FormsModule. Your component needs child component ABC, import ABC. And for simple scenarios, standalone is a bit easier. Bootstrapping can be a bit challenging, which is why the Angular CLI and language services are trying to help with that. ngModules shine when there are a set of components all with similar importing needs. And you still can use them for that if you wish.

Thank you! Wishing you and yours a wonderful 2025 as well. 😊

Happy Holidays! 😊

Happy Holidays! 😊

Should be an exciting year for Angular in 2025!

All the best in 2025! 🎉

Thank you! Happy Holidays! 😊

Yes! Peace on earth for 2025. 😊

Thank you! Happy Holidays! 😊

Happy Holidays to you too! 🎄😊

Thank you! All the best to you and yours. Happy Holidays! 😊

Thank you! The Angular team is currently discussing how best to incorporate signals into forms. From the Angular roadmap: "We plan to analyze existing feedback about Angular forms and design a solution which addresses developers' requirements and uses Signals for management of reactive state." Link: github.com/angular/angular/blob/8c5db3cfb75700dd64f4c8c073554c7086835950/adev/src/content/reference/roadmap.md It is currently unclear whether signal-based forms will replace both reactive forms and template-driven forms, whether it will attempt to unite them, or whether signal features will be added to both types of forms. There are many goals with this project, including: 1) Make observables optional. Currently every Angular project automatically downloads RxJS because it uses it for many of its features, including valueChanges and statusChanges in reactive forms. 2) Manage change detection using signals. As Angular moves toward Zoneless components, it depends more and more on using signals to mark change detection. So there is a desire to manage form inputs with signals as well. We'll know more as we start to see prototypes and/or designs come in 2025.

Glad it was useful. 😊 To answer your question, we would use the same techniques we've been using for years ... depending on the application: - Use an event tied to the select box - Use a property setter on the selectedVehicle property - Use a behaviorSubject - Others?

Thank you! Signals are a "game changer" for Angular!

Excellent! I'm happy it was helpful. 😊

That is very kind of you to ask! Currently, I only have one course on Pluralsight: "RxJS and Angular Signals Fundamentals". Thought it's currently over 1 year old and doesn't have the latest signal features. The other Pluralsight courses have been retired. Pluralsight would no longer allow me to update the "Angular: Getting Started" course. ☹ If you are learning Angular from scratch, you could still start with the "Angular: Getting Started" for the basic concepts. Then move on to my "Angular Topics" playlist for more information on newer features: kzbin.info/aero/PLErOmyzRKOCr07Kcnx75Aqh6PWSbIokPB All the best on your learning journey!

That's so kind of you to say. Thank you! 😊

I'm glad you found it useful. Thank you! 😊

Yes. When the resource declaration is processed at runtime, the loader function runs. If you specify the `request` property of the resource, the loader will re-run any time the `request` signal changes. It may *not* issue the HTTP request if you have logic in the loader function preventing it. For example, this: private filmResource = rxResource({ request: () => ({ vehicle: this.vehicleService.selectedVehicle(), index: this.movieIndex() }), loader: ({request}) => { if(request.vehicle) { return this.http.get<Film>(request.vehicle.films[request.index]); }; return of(undefined); }, }); It won't issue the HTTP request unless the selectedVehicle has a value (isn't undefined).

@@deborah_kurata Thanks, just some general question, it seems Angular is releasing more and more versions on signals which is great, but the thing is, should we wait for a stable one? for instance, now that we have resource and linked signal, it seems that before and after of these changes angular saves us lot of coding, what do you think?

The first "...Loading" message comes from Stackblitz. Are you using Stackblitz or some other editor? (It's basically irrelevant for the code we are writing. I just pointed it out because it appears when using Stackblitz. Sorry for the confusion.)

@deborah_kurata Ah ok now is clear. When I use Stack blitz, appear but when download the code and use VSCode I don't see it 🙂

Fico feliz em saber que a dublagem funciona bem para você. Tudo de bom! 😊

I'm glad you found it useful! Thanks! 😊

That is so very kind of you to say. Thank you! Glad you are a part of the Angular community. 😊