Creating a Data Service | Services & Dependency Injection | Angular 12+

In the last lecture we learned about heirarchical dependency injection and how it works. In this lecture, let's understand one drawback of heirarchical dependency injection.
In this lecture, we are going to create a simple data service and we are going to use it in order to understand the drawback of heirarchical dependency injection.

[@user-hd8dm5ur3i]

The Greatest movie that helped me to open my eyes on DI
Much respect !

[@sasikaadesh8184]

Excellent explanation. Thank you very much!

[@vrb199]

Amazing explanation, thank you so much

[@MillieM2018]

thanks so much, explain and demo DI very clear, will follow your course instead of pluralsight

[@jjuliefrance]

I watched the 4 previous videos, appreciated the way you introduce us to the importance and interest of dependency injection rather than using a service as a simple class that should be instantiated in the component. I appreciated the focus you made on hierarchy in injections, and the risks that comes with as long as the service is specified in the providers array of a child component. But I was expecting all this was to introduce us to the importance of the @injectable decorator at the end. Isn't it better to use it and always import a service from module.ts. As for now, it's what I've always done in my case studies.

[@shubhamjaiswal5077]

You are Amazing 🙂

[@techie2903]

Thank you very much sir

[@OmarTabaaRajla]

since we don't use Providers in angular14, how would the hierarchical injection work?? In Angular 14 as we create a service we get the Injectable({ providedIn:'root'}), so doesn't that mean that this injection is on the root-level??

[@maheshsirsat1811]

i implemented ... when i am adding it is succesfully adding also showing new and extsting data both but problem is when i am reploading it remain as it is without new data

[@mohiburrahman5639]

you can make it by routing also!!

[@zeleoz463]

in this example, ngOnInit is calling again, when we add another user. But is ngOnInit supposed to run only once during initialisation? Normally we use an extra method like updateData() incase we add/remove data from database?

[@Avinash-P.]

This happened because of two way binding, as soon as property username and status got updated, it triggered method of user adding, and then because array got changed, for loop got executed

[@sheshikalasheshi7116]

css code and html code please provide me sir

[@CHANDRASHEKHAR-hk8sq]

wher wil get source code

[@procademy]

github.com/manojjha86/complete-angular-13-course

[@saiviswanath3994]

Thanks for the link... @proacademy