Great video I love how you show all of your points using examples and not just assuming people can learn just by being told the concepts. Very nicely done.
Quick question Do we have to use same instance of TodoService to make it work with signals, instead of => {providedIn: root} can we use => providers:[MyService] But then what is the point of Signals then, i can build the same functionality without signals using shared service. PS: what i am trying to understand is that what advantage signals provides here then.
Good question. Yes, we need to have same instance of service, otherwise we cannot share the same signal. The benefit of signals is more related to reactive programming. For example, in an add to cart application, we can share data through service, but if the data changes that will not be notified to the other components unless we use a Subject mechanism or Emitter mechanism. But this will be solved when we use Signals. Also, Signals are recently introduced, and some APIs are getting changed. So, we may expect more features in the upcoming angular releases.
thank you sir for a good and short compilation of the whole theme one question about your real life example: when creating an effect for calling refreshCart() function you said "whenever my cart signal is changed". And there is no single signal value used inside the effect function. Does it mean that effects listen ALL signals that are in the scope of a component (meaning every signal that is stored inside cartService or other dependencies)? Or does it happens because you're actually calling set function of your signal inside of refreshCart (which in it's turn is called inside an effect)?
Very good question. The effect is triggered because of this line of code. this.cartService.cart() in the for loop. As I am using the cart signal inside the refreshCart function, whenever its value changes the effect will be triggered.
Sir please make a video of project using advanced concepts. Also now angular 18 is out and i am waiting for your videos to know in simple way angular 18 features. Btw way i want to tell you that i switch from my company by learning angular from your zero to hero and hero to superhero series. Whoever asks me i share your channel. Its best and simple. Thanks.
Thank you so much 👍 So happy to hear that my videos helped you in your career advancement. Definitely I will create a video on complete project using advanced concepts.
Okay, so looks like Angular team want's to stop using ReactiveX(RxJS) - and use their own approach istead. Looks like main idea of signals - remove third party RxJS from Angular, am I right ?
Reactive programming is always good and Angular is moving towards the same. We still need RxJS. Also angular is improving performance in many ways. One such way is through Signals.
awesome!!!! Thanks for detailed explanation, Please make a complete tutorial series on angular 18 with all new concepts.
Nice idea. I will create one video.
Hats off to you🎉, the simplest tutorial of signal
Thank you so much 🙏
Amazing, complete video, Thanks!
Thank you so much 😊
This is basically Angular implementing React. Now we have fewer reasons to use React, lmao.
Yes :)
Great video I love how you show all of your points using examples and not just assuming people can learn just by being told the concepts. Very nicely done.
Thanks a lot 🙏
Very very useful and understandable example. Thanks you.
Thank you so much 🙏
learned with pratical examples
Thanks
Your every video is ahead of time or I can say AOT 😂 kudos to you 🎉👍
Thank you so much 😀
Great video, thank you sir
Thank you so much
Quick question Do we have to use same instance of TodoService to make it work with signals,
instead of => {providedIn: root}
can we use => providers:[MyService]
But then what is the point of Signals then, i can build the same functionality without signals using shared service.
PS: what i am trying to understand is that what advantage signals provides here then.
Good question. Yes, we need to have same instance of service, otherwise we cannot share the same signal. The benefit of signals is more related to reactive programming. For example, in an add to cart application, we can share data through service, but if the data changes that will not be notified to the other components unless we use a Subject mechanism or Emitter mechanism. But this will be solved when we use Signals. Also, Signals are recently introduced, and some APIs are getting changed. So, we may expect more features in the upcoming angular releases.
Thanks a lot
Most welcome
thank you sir for a good and short compilation of the whole theme
one question about your real life example: when creating an effect for calling refreshCart() function you said "whenever my cart signal is changed". And there is no single signal value used inside the effect function. Does it mean that effects listen ALL signals that are in the scope of a component (meaning every signal that is stored inside cartService or other dependencies)? Or does it happens because you're actually calling set function of your signal inside of refreshCart (which in it's turn is called inside an effect)?
Very good question. The effect is triggered because of this line of code. this.cartService.cart() in the for loop.
As I am using the cart signal inside the refreshCart function, whenever its value changes the effect will be triggered.
Good concelt sir❤👌
Thank you so much
Sir please make a video of project using advanced concepts. Also now angular 18 is out and i am waiting for your videos to know in simple way angular 18 features.
Btw way i want to tell you that i switch from my company by learning angular from your zero to hero and hero to superhero series. Whoever asks me i share your channel. Its best and simple. Thanks.
Thank you so much 👍 So happy to hear that my videos helped you in your career advancement. Definitely I will create a video on complete project using advanced concepts.
I am still not clear how we know that effect will not trigger infinite changes?
Effect will trigger infinite changes only when we are setting some value inside the effect which triggers another effect and the loop continues.
Sir do you have the project in GitHub?
Yes. You can find in the same GitHub repo.
@@WebTechTalk the link please
@@mraihiamine2907 github.com/freelancer-surender/Angular-General
Thank you so so so much sir 🥰
Why you stopped sharing github for advanced concepts? Can you please share them?
I usually push the code once after the video is published. You can check now.
Its same like react usestate as I see
Yes. And effect is somewhat similar to useEffect.
It's very disappointing and discouraging that we don't have any English-speaking individuals who can effectively teach others in a proper way.
Sorry bro I am not a native English speaker
Well u try teaching this subject nothing stopping, or u saying ur English is not up to spec😂
Okay, so looks like Angular team want's to stop using ReactiveX(RxJS) - and use their own approach istead.
Looks like main idea of signals - remove third party RxJS from Angular, am I right ?
Reactive programming is always good and Angular is moving towards the same. We still need RxJS. Also angular is improving performance in many ways. One such way is through Signals.
@@WebTechTalk thanks :)