💥 Learn Angular Forms in-depth and start building complex form controls with ease💥 🔗 10% discount for the first 10 students - bit.ly/advanced-ng-forms-discounted 💡 Short Frontend Snacks (Tips) every week here: Twitter - twitter.com/DecodedFrontend Instagram - instagram.com/decodedfrontend LinkedIn - www.linkedin.com/in/dmezhenskyi
I just want to say, i’m crazy about your courses and tutorials. You really have a gift for teaching, you dive deep into subject and talk about complex things which others often avoid do to the complexity. This channel (and also your paid courses) are such a refresher for Angular community.. Keep up the great work!
I absolutely love angular and [ngTemplateOutlet] is one of my favourite topics because they allow my template to be extremely reusable. It is indeed very powerful in terms of functionality.
Another excellent video. Well structured, clearly expained. Three parts with small changes enhanced the concepts. Recap helps the viewers remember what has learned. Thank you so much and happy holidays!
I don't speak English (I'm Brazilian), but your explanation is so clear and concise that even if I don't know much English I can understand 98% of what you say. By the way, I love your content.
One more useful video, thanks a lot. Small remark: content projection can also be used in combination with ng-template approach when we use content projection to provide the template to be instantiated inside the recipient component (instead of using @Input for this).
That is exactly what I was thinking about at the end of the video. I think that Dmytro wanted to show us new Angular feature instead - ngTemplateOutlerInjector which is also very cool by the way :)
Hey guys :) Yes, you are right (you both :) ). Actually, many things could be accomplished in many different ways, and "the best" solution is usually very dependent on the particular details and your goals. The solution in the video was chosen just for the demonstration of the ngTemplateOutlerInjector feature staying in the same and familiar context of the WeatherComponent component.
My most sincere congratulations. You have achieved something very difficult, explaining a complex Angular concept with a simple example and even showing useful tricks like $implicit, context and injector. Thank you very much! On the other hand, for me it is very strange to place the tags after the content in which they are going to be rendered. But I guess it's the only option to do it both inside and outside a component and without projection of .
Again, High Quality Content, I came across this templateOutlet many times but couldn't get it left alone it's benefits, Even the official docs didn't do the justice (maybe it's me that it didn't reflect with me). This time I think, you can't cherish the benefits or fruits of declarative approach if haven't gone through the imperative approach like you did with the examples. I know the effort and time it takes to come up with such example's kudos to that. Although I have more experience with Angular than Vue, but in Vue (I think) they are called scoped slot and I have used it well but coming to Angular I didn't get the templateContext it until this Good, Lengthy video. After knowing this concept now, I think Projected Content don't have luxury of Context. What else?
Can you pls explain content projection 1. With slots 2. With styling - do we need to add the styles in the projected component or in the component where the content is passed ? When viewencapsularion is emulated the ngcontent and nghost classes in Dom seems different Pls explain them as well. Thanks
Great content and example, as always. One disadvantage of the ng-template context is that is not typified in when used (let-state) this could be a big problem on refactoring. I hope angular does something about this.
Great stuff, would it be possible to have another video in the future for more advance use cases on ngTemplateOutlet as well as typing the templateOutlet with the Angular 16 features.
Not going to lie, you're a damn legend. But I'm only left a bit with my head scratching around 29:43 - does injecting the Injector provide the reference of the WeatherWidgetComponent? That feels almost a bit "magical" to me! How was the problem with the lack of the component reference solved before? Did people simply pass the function into the ngTemplateOutletContext? I can't remember if you did any blog content for these injectors, but if you didn't I would really, really love those. Thank you for making things easier for us! Without you, I would have been lost in Angular long ago. Nobody touches upon more advanced topics like you do.
Please do content projection as well mate! After we trip[led our dev team size, we are juti n the process of standardising our components (so not every squad reinvents the dialog, the context-hint bar, etc). We have a bunch of good and keen Angular devs, but also many "fullstack :D" ppl not very comfortable with the framework. explaining to them how to create reusable components is so difficult, but this one is a great overview of embedded templates! Would be awesome to ahve content projection as well.
Another great video! Thanks a lot for everything you do for us! I really learned a lot from your videos. Yes, we really want the next video with the ng-content tips and tricks.
Hi!! greetings from Colombia!! you videos are excellent and help me a lot to improve my code a 100% Would be nice if you start teaching IONIC with angular!!! Thanks for exists bro!
Watching this video made me realize I know nothing about templates after working 4 years with Angular. I mean I used all of this before but not like this 😅
@@DecodedFrontend i wish your country has a better year in that 2023, wich is very close and thanks for share your knowledge with us, good bless you, your family and your country
Yep, this is exactly the solution to fix typings issue but it also requires additional “dummy” directive for the type inversion. Just a ContextGuard in WeatherWidget won’t work unfortunately.
Using the structural directive syntax *ngTemplateOutlet="templateName; context: { $implicit: variable, color: 'blue' }" we can specify all the information together. I suppose in Angular 14 they extend this to support the injector value
very useful and helpful with of course high quality, not sure if my suggestion is right, because I find this speaking pace seems to me slow, maybe increase a bit speed of speaking would get more attractions. :)
Спасибо, Дмитрий, вы мой Сенсей! В очередной раз благодаря вашим наставлениям я решил две проблемы которые не давали мне спокойно спать)) Спасибо!!! Ждем проекцию контента.
why not just give provide state & action at root or app.component level & inject both at other places where we want to use state & action since that will be one single instance available at all place? also is inject one component in other component good pratice ? cuz generally it is service that we inject
Informative video. I do have a question, why didn't we use ng-content for dynamic content in a widget container. Additionally, I think the widget component should be dummy (no data)
@@DecodedFrontend На жаль, моя англійська не дозволяє зрозуміти всі 100% інформації. Якби були субтитри чи ще кращий курс українською, це було б шикарно)
I'm using your example and it works fine until I want to trigger an Output event on the parent component it doesn't work, but if I put a console.log inside the function I'm triggering the console log prints the data so it's communicating but for some reason it doesn't trigger the event, would you have any ideas as to why this is happening?
You can provide injector (or particular service you need) of WeatherComponent via template context and then from the context provide to the target component as an input and fetch dependencies from there. Maybe there are another workarounds but I heard only about this one.
Suppose I have created a reusable form group control, that utilizes a custom form control itself. I want to reuse this form group control across different forms, the only difference is the validation logic which should be passed from the parent forms. How to achieve it? So the validation path will be something like parent->formGroup control->custom control. N.B. Form group control is also another form control .
Do you have a small Stackblitz with this use case? Because from what I understood you just have to provide a validator via e.g @Input or DI and in the reusable FormGroup and it just has to add this validator calling addValidators method of the FormGroup. But I am quite sure that I am missing something, so the Stackblitz example would help a lot here.
@@DecodedFrontend Unfortunately stackblitz example is not available at the moment. Let me add a bit more. My concept is something like, I have many forms where I have to deal with a group of dropdown. Those dropdowns together generates a data set.(i.e. address section). Now, If I create a custom control with group of dropdowns,so that can write the data section to parent form model, than surely I can reuse this custom control accross different different forms. But may be in some case I have to change the validations. Sometime i may only need a few dropdowns , sometime all dropdown may be mandatory. Now, If I create a custom dropdown input control, and use this inside my custom group of dropdown control, than the scenario would be, Parent form will use the group control, group control will internally use custom dropdown control. Parent will define the validation logic. Hopefully now I was able to clearly explain my concept. Appreciate your time.
i have done something similar to this , Hope it helps have a reusable single input component and by passing a object as input i can switch between different types of inputs(i.e number , text , textarea) yes validations also passed as well (i.e pattern , minlength , required) reusable component should implement ControlValueAccessor, it should also have formgroup with single formcontrol i also had a formgroup in the parent component as well u can also pass custom validation function to this reusable input component as well if the validation doesnt depend on other form fields if it depends on other form fields u have to create validation function in parent component so in parent component template , u will paste this template of the reusable component passing the object for telling which type of input and validations the formcontrol in parent component also needs the same validations for it to work properly
Hi Dymtro, you content is really great and I am from India and I liked it so much, can I know how you check library source code in vs code itself in same project?
Hi :) It is actually not the "source code in the same project". I just had another VS code window with angular source code opened and on post-production I just cut the transition, so it looks like I jumped immediately to source code which is not really true.
Im trying to pass method inside context. I want trigger this method with click. Now i'm able to pass function, but is triggered no only from click. Have u ever tried same thing?
Great!! Just question. How di you access ngtemplate direttive file from vs code? If i ctrl +click the ngtemplateoutelet i see only the d.ts file and not the typescript.
Im trying to build custom table using angular material table, providing custom table row using ngTemplateOutlet is not working or im missing something, any advice thanks
Dog Breed here mat-card has children like mat-card-header/content and mat-card-header have child like mat-card-subtitle this snippet is from angular material and i want to know the effective way for us to achieve this in our projects its basically how to create custom component that acts like a tag in angular
Can the template outlet use components that have their own template outlets, who in turn have their own template outlets (recursive template outlets-ish) ?
Great tming, hello I have lots of nesting in html template(I'm working with forms) and I was thinking aoubt using template to make it more readable. Is it good idea or should I solve in another way?
Hi, Thanks for your video ! Is this approach better than using @ContentChild ? The use of @ContentChild seems more "appropriate" as the custom template is defined inside my component selector rather than outside. Or does it depend on the use case ? If there are multiple components that need to override the template, the @Input will be more convenient as the template will be defined only once. Whereas it will be defined inside each component with the use of @ContentChild ?
@@DecodedFrontend The truth is I watched the entire video, as usually. I think your concerns regarding previous one, about custom builders, are not relevant to the stuff you are doing. These are the best, the deepest and well explained tutorials on the net. They are simply not for everyone. Thank you.
![Angular Design Patterns - Bridge [Advanced, 2020]](http://i.ytimg.com/vi/2rQOu9TmuxE/mqdefault.jpg)
![Angular Design Patterns – Bridge [Advanced, 2020]](/img/tr.png)
![Tee Grizzley - Blow for Blow (feat. J. Cole) [Official Video]](http://i.ytimg.com/vi/wNLN5xsx5dc/mqdefault.jpg)
💥 Learn Angular Forms in-depth and start building complex form controls with ease💥
🔗 10% discount for the first 10 students - bit.ly/advanced-ng-forms-discounted
💡 Short Frontend Snacks (Tips) every week here:
Twitter - twitter.com/DecodedFrontend
Instagram - instagram.com/decodedfrontend
LinkedIn - www.linkedin.com/in/dmezhenskyi
please create a video on content projection.
Okay :)
Does not exist in the world, enough recognition for this guy! Absolute unit of a teacher!
Дякую, зрозуміле пояснення теми 👍
Дуже дякую за фідбек 😊
I just want to say, i’m crazy about your courses and tutorials. You really have a gift for teaching, you dive deep into subject and talk about complex things which others often avoid do to the complexity. This channel (and also your paid courses) are such a refresher for Angular community.. Keep up the great work!
I absolutely love angular and [ngTemplateOutlet] is one of my favourite topics because they allow my template to be extremely reusable. It is indeed very powerful in terms of functionality.
completely agree!
Another excellent video. Well structured, clearly expained. Three parts with small changes enhanced the concepts. Recap helps the viewers remember what has learned. Thank you so much and happy holidays!
Thank you, I am glad that you liked the video. Have a great holidays as well :)
I don't speak English (I'm Brazilian), but your explanation is so clear and concise that even if I don't know much English I can understand 98% of what you say. By the way, I love your content.
Nobody in youtube teaches angular like this depth as you! Thank you very much and keep teaching us such valuable concepts.
Дмитрий, спасибо большое! Очень понятно и подробно объясняете, одно удовольствие смотреть Ваши ролики.
One more useful video, thanks a lot. Small remark: content projection can also be used in combination with ng-template approach when we use content projection to provide the template to be instantiated inside the recipient component (instead of using @Input for this).
That is exactly what I was thinking about at the end of the video. I think that Dmytro wanted to show us new Angular feature instead - ngTemplateOutlerInjector which is also very cool by the way :)
Hey guys :) Yes, you are right (you both :) ). Actually, many things could be accomplished in many different ways, and "the best" solution is usually very dependent on the particular details and your goals. The solution in the video was chosen just for the demonstration of the ngTemplateOutlerInjector feature staying in the same and familiar context of the WeatherComponent component.
Great job Dmytro! NgTemplateOutlet is a powerful directive that everyone should use often
My most sincere congratulations.
You have achieved something very difficult, explaining a complex Angular concept with a simple example and even showing useful tricks like $implicit, context and injector.
Thank you very much!
On the other hand, for me it is very strange to place the tags after the content in which they are going to be rendered. But I guess it's the only option to do it both inside and outside a component and without projection of .
Thanks a lot for the explanation. It's amazing!
I would like to know more about content projection.
There's never enough videos about ngTemplateOutlet 🤯
Really interesting video! I would like to have a video related to content projection as well :)
I will be glad to make it ;)
this was exactly what i needed. thanks for the video
Insightful lesson, I have a use case for it.
Got a reusable table I need to wire next year and this may be the solution I am gonna run with
Yep, reusable table is a perfect use case and I think ngTemplateOutlet will perfectly work for you.
Thanks for your greate video about template outelet. I've recently used it to create a dynamic mat-search-select. thanksssssss
Great work
I'd love to see a video on content projection
I used to use NgTemplateOutlet and NgTemplateOutletContext directive to render repetitive code in the same component. It's really useful.
U make my learning curve easy now :). This is the missing spot for more advanced concepts. Cheers
I'l new in the game and your videos are very useful -. Thanks
U r awesome Dmytro.. ❤ from India Please keep making videos on important stuff of angular. Very helpful..
Very Informative Pure Class 🙂
Thank you for your feedback! I am glad that you liked it.
I've learned so much from your videos. Your content covers topics I haven't found anywhere and it has helped me a lot in my work. Thank you so much!
Great explanation... Thanks. I will share this video with ours juniors, for better understanding...
Awesome, thank you for supporting ! 🙏🏻
Thaks for sharing. This content is gold
Muito bom Parabéns, a qualidade está muito boa de seus vídeos continue assim amigo!
Again, High Quality Content,
I came across this templateOutlet many times but couldn't get it left alone it's benefits, Even the official docs didn't do the justice (maybe it's me that it didn't reflect with me).
This time I think, you can't cherish the benefits or fruits of declarative approach if haven't gone through the imperative approach like you did with the examples. I know the effort and time it takes to come up with such example's kudos to that.
Although I have more experience with Angular than Vue, but in Vue (I think) they are called scoped slot and I have used it well but coming to Angular I didn't get the templateContext it until this Good, Lengthy video. After knowing this concept now, I think Projected Content don't have luxury of Context. What else?
Can you pls explain content projection
1. With slots
2. With styling - do we need to add the styles in the projected component or in the component where the content is passed ?
When viewencapsularion is emulated the ngcontent and nghost classes in Dom seems different
Pls explain them as well.
Thanks
Thank you for suggestion :) I will definitely cover those things
Great content and example, as always. One disadvantage of the ng-template context is that is not typified in when used (let-state) this could be a big problem on refactoring. I hope angular does something about this.
Yeah...I also hope that it will be supported out of the box.
Great stuff, would it be possible to have another video in the future for more advance use cases on ngTemplateOutlet as well as typing the templateOutlet with the Angular 16 features.
Amazingly taught. Very informative. Thanks for this❤
Great video! I would also be interested in a video about content projection and when to use content projection / ngTemplateOutlet
Great video Dmytro. Would be great to have a course like the forms one, but for those Angular core middle or advanced topics.
This is very interesting. I plan 2 new courses in the next year. Let's see what i come up with ;)
@@DecodedFrontend Great Dmytro. Many thanks for your quick reply.
Content projection 🙏🏻
Fantastic video, extremely helpful! Thank you!
Thank you! The best content about Angular.
Awesome as usual. Quick correction: @ 9: 50 you mean IMPERATIVE paradigm. You then correctly reference implementing via a DECLARATIVE paradigm.
very useful vid! thank you for being generous to us. you are really a smart guy!
Not going to lie, you're a damn legend. But I'm only left a bit with my head scratching around 29:43 - does injecting the Injector provide the reference of the WeatherWidgetComponent? That feels almost a bit "magical" to me! How was the problem with the lack of the component reference solved before? Did people simply pass the function into the ngTemplateOutletContext? I can't remember if you did any blog content for these injectors, but if you didn't I would really, really love those. Thank you for making things easier for us! Without you, I would have been lost in Angular long ago. Nobody touches upon more advanced topics like you do.
Please do content projection as well mate!
After we trip[led our dev team size, we are juti n the process of standardising our components (so not every squad reinvents the dialog, the context-hint bar, etc).
We have a bunch of good and keen Angular devs, but also many "fullstack :D" ppl not very comfortable with the framework.
explaining to them how to create reusable components is so difficult, but this one is a great overview of embedded templates! Would be awesome to ahve content projection as well.
Another great video!
Thanks a lot for everything you do for us! I really learned a lot from your videos.
Yes, we really want the next video with the ng-content tips and tricks.
Thank you! Very useful video!!!
You are welcome:)
So good video..... Thank you so so much
muchas gracias, excelente video, nuevo subs
Greate video, please make the ng-content video!!!
Somehow I got distracted by your cat : )
Excellent video Dmytro
😁
another awesome lesson!
Thanks 🙏🏻
Another great video. Thanks ❤ and Happy new year 🎉🎉
Hi!! greetings from Colombia!! you videos are excellent and help me a lot to improve my code a 100% Would be nice if you start teaching IONIC with angular!!! Thanks for exists bro!
Watching this video made me realize I know nothing about templates after working 4 years with Angular. I mean I used all of this before but not like this 😅
You can't imagine how often it happens to me as well :D
Great video, thanks, i think that's an amazing feature
Yep, I am agree!
@@DecodedFrontend i wish your country has a better year in that 2023, wich is very close and thanks for share your knowledge with us, good bless you, your family and your country
@@haroldpepete Thank you so much, I appreciate it so much.
Thanks
Wow! Thank you so much for support!
You could set a type of TemplateRef using ngTemplateContextGuard
Yep, this is exactly the solution to fix typings issue but it also requires additional “dummy” directive for the type inversion. Just a ContextGuard in WeatherWidget won’t work unfortunately.
Using the structural directive syntax *ngTemplateOutlet="templateName; context: { $implicit: variable, color: 'blue' }" we can specify all the information together. I suppose in Angular 14 they extend this to support the injector value
very useful and helpful with of course high quality, not sure if my suggestion is right, because I find this speaking pace seems to me slow, maybe increase a bit speed of speaking would get more attractions. :)
Спасибо, Дмитрий, вы мой Сенсей! В очередной раз благодаря вашим наставлениям я решил две проблемы которые не давали мне спокойно спать)) Спасибо!!! Ждем проекцию контента.
Could you create a video on angular universal?
thank you
why not just give provide state & action at root or app.component level & inject both at other places where we want to use state & action since that will be one single instance available at all place? also is inject one component in other component good pratice ? cuz generally it is service that we inject
Please create video on ng-content
Informative video. I do have a question, why didn't we use ng-content for dynamic content in a widget container. Additionally, I think the widget component should be dummy (no data)
¡Gracias!
Thank you so much for your support! I appreciate it :)
лайк не глядя!
хотелось бы ещё субтитры или русскоязычную версию
Зачем. У Димона инглишь очень хороший и понятный. Это ты ещё гайды индусов не слушал :).
я очень хочу пустить субтитры на Украинском, но писать их это примерно так же долго как создавать видео. Поэтому я пока отложил это дело :(
инглиш для разработчика маст хев так сказать!
@@DecodedFrontend На жаль, моя англійська не дозволяє зрозуміти всі 100% інформації. Якби були субтитри чи ще кращий курс українською, це було б шикарно)
luka doncic teaching angular in the offseason
thanks lot
Luka Doncic at it again!
How do you create a typed template context and template ref
Happy New Year, Dmytro) Wish you all the best:)
Thank you, Gagik! Happy New Year!
I'm using your example and it works fine until I want to trigger an Output event on the parent component it doesn't work, but if I put a console.log inside the function I'm triggering the console log prints the data so it's communicating but for some reason it doesn't trigger the event, would you have any ideas as to why this is happening?
What's the purpose of exclamation point (!) Here?
Thanks for your question :) It tells TypeScript that the property won't have an initial value and and will be setup later in runtime.
It is the non-null assertion operator to tell the compiler this variable is not null or undefined.
wow!!!
How can the solution that the ngTemplateOutletInjector brings be done in Angular versions lower than 14?
You can provide injector (or particular service you need) of WeatherComponent via template context and then from the context provide to the target component as an input and fetch dependencies from there. Maybe there are another workarounds but I heard only about this one.
💥
Suppose I have created a reusable form group control, that utilizes a custom form control itself. I want to reuse this form group control across different forms, the only difference is the validation logic which should be passed from the parent forms. How to achieve it? So the validation path will be something like parent->formGroup control->custom control.
N.B. Form group control is also another form control .
Do you have a small Stackblitz with this use case? Because from what I understood you just have to provide a validator via e.g @Input or DI and in the reusable FormGroup and it just has to add this validator calling addValidators method of the FormGroup. But I am quite sure that I am missing something, so the Stackblitz example would help a lot here.
@@DecodedFrontend Unfortunately stackblitz example is not available at the moment. Let me add a bit more. My concept is something like, I have many forms where I have to deal with a group of dropdown. Those dropdowns together generates a data set.(i.e. address section). Now, If I create a custom control with group of dropdowns,so that can write the data section to parent form model, than surely I can reuse this custom control accross different different forms. But may be in some case I have to change the validations. Sometime i may only need a few dropdowns , sometime all dropdown may be mandatory.
Now, If I create a custom dropdown input control, and use this inside my custom group of dropdown control, than the scenario would be, Parent form will use the group control, group control will internally use custom dropdown control. Parent will define the validation logic. Hopefully now I was able to clearly explain my concept. Appreciate your time.
i have done something similar to this , Hope it helps
have a reusable single input component and by passing a object as input i can switch between different types of inputs(i.e number , text , textarea)
yes validations also passed as well (i.e pattern , minlength , required)
reusable component should implement ControlValueAccessor,
it should also have formgroup with single formcontrol
i also had a formgroup in the parent component as well
u can also pass custom validation function to this reusable input component as well if the validation doesnt depend on other form fields
if it depends on other form fields
u have to create validation function in parent component
so in parent component template , u will paste this template of the reusable component passing the object for telling which type of input and validations
the formcontrol in parent component also needs the same validations for it to work properly
@@brucearmstrong5536 Could you please share the snippet/sample/ a tutorial video?
@@user-rp9iis1en6h There are plenty of sources in internet
Hi Dymtro, you content is really great and I am from India and I liked it so much, can I know how you check library source code in vs code itself in same project?
Hi :) It is actually not the "source code in the same project". I just had another VS code window with angular source code opened and on post-production I just cut the transition, so it looks like I jumped immediately to source code which is not really true.
@@DecodedFrontend oh okay thank you.
Im trying to pass method inside context. I want trigger this method with click. Now i'm able to pass function, but is triggered no only from click. Have u ever tried same thing?
Please upload your course on Udemy
Great!! Just question. How di you access ngtemplate direttive file from vs code? If i ctrl +click the ngtemplateoutelet i see only the d.ts file and not the typescript.
Im trying to build custom table using angular material table, providing custom table row using ngTemplateOutlet is not working or im missing something, any advice
thanks
Why can't we just pass actions using let-action the same way we pass let-state? That seems easier.
Dog Breed
here mat-card has children like mat-card-header/content and mat-card-header have child like mat-card-subtitle
this snippet is from angular material and i want to know the effective way for us to achieve this in our projects
its basically how to create custom component that acts like a tag in angular
thumb up for cat behind
Can the template outlet use components that have their own template outlets, who in turn have their own template outlets (recursive template outlets-ish) ?
Sure, they can have :)
has anyone told you you look like Luka doncic? thanks for the videos btw
Great tming, hello I have lots of nesting in html template(I'm working with forms) and I was thinking aoubt using template to make it more readable. Is it good idea or should I solve in another way?
You set your cover picture exactly like a country man from east...
You can move out of an eastern village but the village will never move out of you.
Hi,
Thanks for your video !
Is this approach better than using @ContentChild ?
The use of @ContentChild seems more "appropriate" as the custom template is defined inside my component selector rather than outside.
Or does it depend on the use case ?
If there are multiple components that need to override the template, the @Input will be more convenient as the template will be
defined only once.
Whereas it will be defined inside each component with the use of @ContentChild ?
Nice Cat:)
Thanks :)
🙏🙏🙏
I had been very focused until I saw that cat behind.
The cat stole the show.
that’s true 😁
@@DecodedFrontend The truth is I watched the entire video, as usually. I think your concerns regarding previous one, about custom builders, are not relevant to the stuff you are doing. These are the best, the deepest and well explained tutorials on the net. They are simply not for everyone. Thank you.
👍👍👍👍✅
injector = inject(Injector)
injector = inject(Injector) lul. Great video tho
Tallent
Kinda complex subject.
Good topic