Episode 8 | Angular Change Detection Strategy

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.

[@lunadeluna69]

Thanks for awesome video. Love the concrete and easy to follow example.

[@ritachoudhary8404]

Awesome video. best explanation for change detection strategy

[@soumyajeetbai]

thanks bro for your valuable examples. 🙏

[@TheUltimateTrainJourney]

This video answers many other questions and also encouraged us to read more about interesting js questions

[@kalankasiyambalapitiya7615]

Good explanation , thanks and keep up the good work !!!!!

[@ashishnayak2666]

Clear explanation ty bro...

[@cw5948]

I appreciate that you covered immutability. A lot of lessons on this subject don't discuss this, which is a problematic oversight.

[@MrHesamuddin]

Thank you so much, please keep making such video.

[@nirajtathe2172]

Thanks for the explanation. It is easy to understand.

[@ragucool9468]

How to make reusable component in angular ? Kindly make video bro.... thanks advance . Videos simply super

[@nadeemkh100]

Thank you Man, Perfect than many articles.

[@hemantgajbe8500]

Thanks very nicely explained

[@sourishdutta9600]

Keep the good Work. You are an amazing man.

[@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…

[@patelhetal2232]

Good Video.Thank you.

[@sampetroda1373]

Thanks. it is a good article

[@chandukanth6875]

But splice will change the string? Is that means it is changed? Mutable?

[@TheOwlWhoKnows56111]

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.

[@SaikatsTutorial]

Thanks for commenting. Here I was trying to show, no string method operates on actual string being immutable, rather it returns a new string.

[@anantshekhar698]

this change detection strategy works upon @Input properties only or normal properties also??

[@orz5516]

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!

[@vinodnkr6992]

How about when dealing with strings then? Consider passing a string , seems this concept wont work with immutable.. isn't it ?

[@nanasarathi]

Thanks... It was really nice

[@SandeepKumar-ix2gt]

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.

[@Gijera]

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.

[@hemeshjaiswani6654]

nicely cleared

[@darioribas3001]

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.

[@sankarprasadpanda9431]

Loved it!! Learnt something..Subscribed :)

[@SaikatsTutorial]

Thanks

[@TheUltimateTrainJourney]

Yesterday in interview asked this question but I didn't know this

[@julianalvarez9810]

starts at 3:41

[@vothuong08]

it"s nice

[@DevendraKumar-hw9rg]

U can change string with splice

[@sanjayidpuganti8367]

Splice changes the string in place 1:46

[@SaikatsTutorial]

splice is Array function

[@sanjayidpuganti8367]

Saikat's Tutorial sorry my bad

[@mayankvora8116]

strings are mutable, use splice.

[@gonzalosurribassayago4116]

Hello send me the link code thanks

[@SaikatsTutorial]

github.com/mysupermate/demoApp