For those of you wondering why at 4:57 there is no "Channel Name Observable Called", this is because the selectors are even more powerful than it seems: the observable is called only if the value of that particular portion of the state CHANGE, this makes the code even more performant
Thanks a lot for taking out your time to make these videos. I can see that you have recorded these videos during midnight by sacrificing your sleep. You are a good man and your content is helpful a lot. May your life be full of happiness. Thanks
We can use but i told you the advantages of using createselector in the previous video. Always it is best practice to use the create selector concept to get the state data into components
at creation of selectors , that CounterState is interface not a store as you said in a tut . it create confusion for me than i saw your gitgub code . naming convention is not good here ,i think it was state actually it was interface , i know inside angle we should give generic type but ahh const getInitialState = createFeatureSelector('state');
For those of you wondering why at 4:57 there is no "Channel Name Observable Called", this is because the selectors are even more powerful than it seems: the observable is called only if the value of that particular portion of the state CHANGE, this makes the code even more performant
Thanks a lot for taking out your time to make these videos. I can see that you have recorded these videos during midnight by sacrificing your sleep. You are a good man and your content is helpful a lot. May your life be full of happiness. Thanks
True
Very clear explanation with best examples. Thanks sir.
I Watch lots of tutorial for ngrx even paid courses , but you explain amazing and using clear approach ! Thanks leela brother
Nicely explained tutorials with examples. Thanks Leela for good work. Keep it up. Your videos are really helpful.
Thanks leela for your great work on these video series
Before starting this video , you are the top in my list for the ngrx. NOT good, not better this is the BEST.
Wow, thanks!
step by step lesson great,Thanks
Great tutorial with clear explanation
thanks for your valuable time for these type of videos, I learned a lot from your videos.
this ngrx thing needs to get automated asap..it makes a developers life so miserable..such a huge learning curve man!
Nice and clean explanation 😊👌
nice explanation
Amazing lesson, thanks 🏆🏆🏆
My pleasure!
thank you for introducing
Amazing
Good Work Leela
Thank you 😊
Super sir
Thanks lot :) just add the link of playlist so it will be handy.
hi @leela
from where you learnt all these?
what if i need to pass counter$ as @Input()? How should I get the actual value of it in child component?
min 6-8 Observable convertion and async pipe--> shorter CODE
what if we have so many keys in one Object. That way we have to make too many selectors?
That depends on the application. We can create selectors but that would not be nice idea. We have to plan according to the application requirement
can we use both concepts in module, is it Good or Bad ?
We can use but i told you the advantages of using createselector in the previous video. Always it is best practice to use the create selector concept to get the state data into components
@@LeelaWebDev like some big state , this scenario will do ? Ahh
Yeah
at creation of selectors , that CounterState is interface not a store as you said in a tut . it create confusion for me than i saw your gitgub code . naming convention is not good here ,i think it was state actually it was interface , i know inside angle we should give generic type but ahh
const getInitialState = createFeatureSelector('state');
done - 22nd Jan
Super sir