Angular Injection Context Explained

[@fahadgaliwango4502]

you make angular concepts simple and easy to understand. thanks since NG2

[@deborah_kurata]

That is wonderful to hear. Thank you so much! 😊

[@d13g0m0r3n0]

Another awesome explanation, Deborah you're wonderful

[@deborah_kurata]

Thank you so much! 😊

[@vd2828]

The content is so useful. Thank you very much.

[@deborah_kurata]

Great to hear that. Thank you! 😊

[@orhancanoguz4423]

Thanks , Professor...

[@deborah_kurata]

You are welcome! Hope it was useful!

[@pranaykhilari7345]

Thanks Deborah. What is the advantage of using inject over constructor base dependancy injection

[@deborah_kurata]

One of the key reasons is that it is more explicit. The code is saying to inject a dependency and assign the reference to a variable. When using a constructor, you have to know the "secret" about what a constructor parameter means. And if you forget the public/private keyword, the magic doesn't happen. And, as shown near the end of the video, you can use inject in places you can't use constructor-based dependency injection.

[@theFijian]

I've used inject in a factory service to inject a service based on a query string param. Much easier then doing it in the constructor

[@osamaabozahra]

Thanks Deborah, you're my favorite teacher great video, waiting for the new one, preferably an advanced one 😀

[@deborah_kurata]

That is so kind of you to say! Thank you! When you say "advanced", do you have something specific in mind?

[@osamaabozahra]

@@deborah_kurata ​There are multiple ones actually: - runInInjectionContext use cases - injector.create function Basically the dependcy injection advanced use cases in a practical way Also another video in my mind is one like the "RxJS in Angular: Terms, Tips, and Patterns" but for signals 😃 Thanks a lot for your videos again

[@deborah_kurata]

@@osamaabozahra I'll definitely add those topics to my list. I do have a video on signals here: kzbin.info/www/bejne/paK8gnpthrKXsNk But I assume you're looking for something a bit more advanced? You could check out my signals play list: kzbin.info/aero/PLErOmyzRKOCrzJ9zUEGgC1zVzVGt3hMmV

[@osamaabozahra]

@@deborah_kurata Thanks Deborah, I have already watched most of your signals playlist, and will recap them. But I meant a full video discussing some of the emerging patterns related to signals and what are the best practices using them.

[@deborah_kurata]

I just posted a video about this today: kzbin.info/www/bejne/qHm0kmeJpcqel6M

[@felipemendietaz4947]

Woow Deborah, I love your explanations, thanks a lot, I came here for your free code camp tutorial about signals. Greetings from Ecuador.

[@deborah_kurata]

Greetings! So great to hear the videos are helpful. Thanks! 😊

[@Mark33090]

very cool, I've only put them in the constructor's () area, didn't know we had options... Is there a preferred place to inject services though, or are they all the same??

[@omararizmendi7574]

Thank you very much for this explanation. A really easy way to understand this topic, thanks.

[@deborah_kurata]

Thank you!

[@ruekkart]

Nice explanation. I came to Angular from a backend background and I loved it, especially because of its DI system. However, I'm now worried about the inject() function because, in the backend world, it is generally considered bad practice to use property injection. It is encouraged to use constructor injection most of the time, mainly to maintain better control over the dependencies of a given class/component/module. What do you think about this?

[@deborah_kurata]

Thanks! I looked at that a bit when I was researching for this post. I came upon this, which provides some background on inject() in a JavaScript world: www.reddit.com/r/Angular2/comments/18ry9m4/the_inject_function_in_angular_is_not_just_a_toy/

[@OlehBiblyi]

Great explanation

[@deborah_kurata]

Thank you!

[@CodingAbroad]

So is using constructor now undesirable? Can we avoid using constructor completely now?

[@deborah_kurata]

Not necessarily undesirable. Yes, you can avoid using the constructor if you want to. But you can use either. Many teams are standardizing on the inject function approach. Others prefer to see the injected services all in one place in the constructor.

[@poojajagtap7349]

Valuable content thanks

[@deborah_kurata]

Thank you!

[@cooleboy50]

Great video Deborah. What is the primary reason that we can only inject within the injection context?

[@deborah_kurata]

Thanks! As per the docs: "The dependency injection (DI) system relies internally on a runtime context where the current injector is available. This means that injectors can only work when code is executed in such a context." angular.dev/guide/di/dependency-injection-context

[@poojajagtap7349]

Thanks Best video

[@deborah_kurata]

Thanks so much!

[@underTaker-d2q]

Something new 🎉 I haven't heard

[@deborah_kurata]

Hope it was useful! 😊

[@ritiksahu5310]

thanks

[@deborah_kurata]

😊

[@RaghavendraKarteek]

HI Madam, please post Angular 17 concepts tutorials as well.

[@deborah_kurata]

Is there a specific topic you're interested in?

[@RaghavendraKarteek]

@@deborah_kurata thanks for your reply. Could you please explain defer concepts and SSR concepts

[@deborah_kurata]

Defer is definitely on my list. I have not tried out SSR, so that one is further down on my list as it will require significant research. 😊

[@RaghavendraKarteek]

@@deborah_kurata thanks for your reply