วีดีโอ

This is wonderful 😮😮😮

So what would be a good implementation in Angular v18 without the linkedSignal? Thanks in advance

❤❤❤

Excellent tutorial. Thanks for all the time and effort that you take to do this for us. You are the best. Wow!

Thats a great addition. Now we just need some way to debounce signals, i don't want to spam the server with requests while the user is typing in the search field. Currently i'm using an rxjs observable with debounce and toSignal for this, but would be great if there was a signal only solution

Thanks so much , i love your explanation so much , Follow you from Egypt

I'll consider this new API as syntax sugar of the way Alex had introduced in this video: th-cam.com/video/aKxcIQMWSNU/w-d-xo.html&lc=UgzLINiOE616VnGxdQB4AaABAg.A8op9H13SrwA96TFOIQYj4

I think this could be very useful for input signals

Awesome video thanks for coming again with such a video🎉🎉

Great video as always. With signals and rxResource API and zoneless, can we conclude that RxJs is no longer needed and also component lifecycle hooks are no longer needed? Thanks for your feedback.

Excellent explanation. I'm about to start a new non-critical project in angular. Should start it with v18 ou v19-rc so that I have access to the RxResource API? Thanks for the advice.

Thank you

Pretty sweet!

👏🏻👏🏻👏🏻

Great

Tutorials from this woman I can confidently auto-like before I start watching them. I've yet to un-like a single one.

Another great video! Thanks Deborah!!

What would we do without you Deborah ☀️ You're an absolute TH-cam gem 💎 Appreciate your work! 🙏

Thank you so much for this video. It's awesome !))

Thanks for sharing, what about errors handling?

my only advice would be at around 3:30... I would have explained more in depth how the relationships between the generics and the incoming arguments work. ie... If you dont pass in a type when calling logSignal.. the type will be inferred by the argument that was passed in etc etc. For example.. calling `logSignal<string>(this.mySignal) would error.. however `logSignal(this.mySignal)` would not.

How do you re initialize the value of the toSignal? I mean if we have a component which is printing some information by using the value we are getting from a toObservable and then passed to a toSignal, when you select another element, first you see the last thing you got from the Observable, and after that you see the new data, how do you clean up the toSignal o re start the initialValue

i've watched a lot of your videos.. this one made me subscribe... thanks.

Interesting (and high quality as always). I couldn't quite work out how I might use this for infinite scroll. Also interesting that they seem to be first classing fetch? I only really use HttpClient for interceptors so that would be nice if it went.

Its sad that angular is slowly facing java's fate... The newer versions are so much better and have so many new features but people just dont want to migrate from the older versions

Teacher 💛

Cool!!! I think Angular team is taking the things forward so passionately! Thanks Deborah, for a clear overview video.

Great new feature!!

Thanks for your videos Deborah, you are a great teacher

Somehow I have a feeling that this new API does a similar thing to what @ngrx/signal-store does with the rxMethod

This is looking amazing. I'll wait until developer preview for this one.

Thanks Deborah for the video. As I understand, using 'resource()' with 'fetch' will be more reasonable for this update?

Simple and very helpful, thanks for this video! You can make a video about named routes? E see named routes when i’m using google cloud console 😊

Do you think “request” is a good name for dependencies?

I wonder if Angular will allow HttpClient to return a Promise instead of Observable. That would remove the next need of rxResource for a lot of apps.

Thanks, teacher Deborah! This is the video I was waiting this week. Now that we have Resource Api, Angular (TanStack) query and SignalStore, what do you think will be the recommended way to easily manage server state (loading, error, success)? Do you think Resource api for server state and SignalStore for local state is a good combination? What do you think could be the best architecture for enterprise applications in modern Angular? Share your GDE thoughts with padawans. 🤩

Hi, Deborah! Love your educational content. We've refactored our old Angular 8 codebase to fully reactive Angular 18 thanks to your videos on signals and home-made signal store. I have a concern about writing the resource locally. It's purely vibes, I don't have data to support it, but doesn't writing to resource locally go against reactivity or declarativity?

Thank you for the useful and interesting information.

Very clear, thanks.

🎉

Nice feature, thank you for the heads up! It could indeed be an easy way to update values both in the browser context and in the persistence via an HTTP call. Maybe you'll show us a nice implementation in November 🙂

And what if a component needs to change the state, but the component itself depends on this state?

Please do some long length application in latest angular and signals and nestjs 🎉❤

Excellent content, Ms. Kurata. For the first time, I found clear explanations about how these operators work. Greetings from Brazil

Great🎉

Great video-straight to the point with clear explanations.

I get that there are situations where you might want to track a signal without having to read its value, but surely it would be better to add an overload to the existing *effect()* function rather than create an entirely new API? effect(() => this.quantity.set(1), [this.selectedProduct]);

Thank you for the video! It's so short and clear

excellent !

Instead of the example you made with http request used in a linkedSignal, should maybe the new angular v19 resource api be more suitable for that case? thanks for the video!