If you are building a large app then you must optimize code by implementing manual change detection process. This video shows how to use change detection strategy in Angular.
Пікірлер: 39
@lunadeluna695 жыл бұрын
Thanks for awesome video. Love the concrete and easy to follow example.
@ritachoudhary84042 жыл бұрын
Awesome video. best explanation for change detection strategy
@cw59485 жыл бұрын
I appreciate that you covered immutability. A lot of lessons on this subject don't discuss this, which is a problematic oversight.
@ashishnayak2666 Жыл бұрын
Clear explanation ty bro...
@TheUltimateTrainJourney4 жыл бұрын
This video answers many other questions and also encouraged us to read more about interesting js questions
@darioribas30015 жыл бұрын
Hi, nice work! Do you know if there is a way I can detach change detector and centralize detectChanges into an event for a child component? I only got it calling detectChanges every place I needed it.
@orz55164 жыл бұрын
question - should i use onPush in every component in my app which has an @input? or only in components with long lists of component (that can hurt my performance) thanks!
@nadeemkh1005 жыл бұрын
Thank you Man, Perfect than many articles.
@soumyajeetbai2 жыл бұрын
thanks bro for your valuable examples. 🙏
@sourishdutta96005 жыл бұрын
Keep the good Work. You are an amazing man.
@kalankasiyambalapitiya76154 жыл бұрын
Good explanation , thanks and keep up the good work !!!!!
@ragucool94682 жыл бұрын
How to make reusable component in angular ? Kindly make video bro.... thanks advance . Videos simply super
@nirajtathe21724 жыл бұрын
Thanks for the explanation. It is easy to understand.
@anantshekhar6983 жыл бұрын
this change detection strategy works upon @Input properties only or normal properties also??
@MrHesamuddin4 жыл бұрын
Thank you so much, please keep making such video.
@chandukanth68752 жыл бұрын
But splice will change the string? Is that means it is changed? Mutable?
@sanchessantos7153 Жыл бұрын
Thanks for video, I am Passing for one problem in my job. The data update only if I to click on the screen or to put one event click()… I am go to test this…
@nanasarathi5 жыл бұрын
Thanks... It was really nice
@vinodnkr69922 жыл бұрын
How about when dealing with strings then? Consider passing a string , seems this concept wont work with immutable.. isn't it ?
@sankarprasadpanda94316 жыл бұрын
Loved it!! Learnt something..Subscribed :)
@SaikatsTutorial6 жыл бұрын
Thanks
@SandeepKumar-ix2gt5 жыл бұрын
Thanks Saikat. This video help me a lots to understand change detection methodology but i have two questions in my mind: 1).changeDetectionStrategy.onpush will only work when reference of object changed then What does the difference make mutable or immutable objects. 2). Why should we use detect or detach method of changeDectorRef ? changeDetectionStrategy.onpush will work as same, in your video if we want to detach changes then we can use changeDetectionStrategy.default and if want to detect than we can use changeDetectionStrategy.onpush . Can you please help to understand we should use changeDectorRef.
@Gijera4 жыл бұрын
For #1 a mutable object is one where its state can be changed and still point to the same reference, while an immutable is an object which cannot change its state. To 'change' it, It requires you to create a whole new object with the changes and reassign it back. Mutable means 'capable of change', while 'immutable' means 'not susceptible to change'. You can think of this 'clone and reassign' process for immutable objects as a sort of 'push'. Hence 'changeDetectionStrategy.onpush'. For #2 I believe the changeDetectorRef allows fine grained control of when these 'change processing' features happen within your code.
@patelhetal22324 жыл бұрын
Good Video.Thank you.
@balinthaui60804 жыл бұрын
The slice function returns with a new string and does not modify the original one. So if you do not save the result of the slice operation in a new var, then the result is lost. The reason you see "example" after the slice is because you are printing the original one, you did not save the result in a new var. Although strings are indeed inmutable, this is not a good reasoning.
@SaikatsTutorial4 жыл бұрын
Thanks for commenting. Here I was trying to show, no string method operates on actual string being immutable, rather it returns a new string.
@hemantgajbe85004 жыл бұрын
Thanks very nicely explained
@sampetroda13734 жыл бұрын
Thanks. it is a good article
@hemeshjaiswani66545 жыл бұрын
nicely cleared
@vothuong085 жыл бұрын
it"s nice
@TheUltimateTrainJourney4 жыл бұрын
Yesterday in interview asked this question but I didn't know this