🔥🔥🔥Do you want to master *Angular Material Themes* like a PRO? Check out my new Workshop where you will find a lot of advanced tips & tricks which will help you to make your themes maintainable, lean & consistent! Limited 50%-off discount is about to expire very soon: 🔗 bit.ly/angular-material-theming-workshop 🔥🔥🔥
I'm really glad I found this channel. Also I would love to commend your selflessness. You totally blew my mind when you recommended another RUclipsrs course, it's not something we see everyday
Very nice examples! I was very surprised to see 2 components in one file in material codebase btw. I think placing 2 components in one does not solve circular deps problem but just masks it really. You should make a video on this topic how to properly resolve circular deps with different techniques =)
Hey Dmytro, thanks for the explanation. One thing I didn't understand exactly - around 7:40, why didn't we get the 'used before declaration' error earlier when we didn't extract the provider into a separate object at the top? We're using the velocity widget component class before declaration in both the cases.
Its because compiler reads files from top to bottom. When WIDGET_PROVIDER was declared at line 5 (it doesn't matter the value of useExisting was invalid in this case) it was known to the compiler at line 13.
Hi! I have a question regarding custom providers: Is there some way to pass an @Input() value to custom provider inside component providers: []? Example: {provide: SOME_TOKEN, useValue: myDynamicValueFromInput} P.S. Thank you for the video!
such a great content, so much usefull information, very good delivery, great examples, but asking to subscribe is such annoying thing, it almost kills all hard work you have done and its hard to keep watching, anyway keep it up!
@@compton8301 I know, but to make good thing better someone should be "that" guy, also not asking to subscribe is a charm, and helps to people subscribe more
🔥🔥🔥Do you want to master *Angular Material Themes* like a PRO? Check out my new Workshop where you will find a lot of advanced tips & tricks which will help you to make your themes maintainable, lean & consistent! Limited 50%-off discount is about to expire very soon: 🔗 bit.ly/angular-material-theming-workshop 🔥🔥🔥
Oh, God! Thank you, man, for the explanation!
I'm really glad I found this channel. Also I would love to commend your selflessness. You totally blew my mind when you recommended another RUclipsrs course, it's not something we see everyday
you always take the best topics and give a good explanation. Thank you sir!
Thanks for feedback 😊
More advanced angular content! Awesome!
Great explanation as always. ⭐
awesome content bro, go on with this great job.
Great explanation of forwardref, thanks! 🙏
Thanks for feedback!
I just watch the angular air episode which is very wonderful and jumped into you channel.
You doing great job keep it up .
Glad you like it! Thank you for your feedback 🙂
Thanks for the advanced Angular vids!
Thank you :)
Thank you Dmytro for such wonderful technical videos and you deserve much much more subscription.
Thank you again!
Another great video from great channel! Thank you!
Thanks dude. This is useful information.
Very nice examples!
I was very surprised to see 2 components in one file in material codebase btw.
I think placing 2 components in one does not solve circular deps problem but just masks it really.
You should make a video on this topic how to properly resolve circular deps with different techniques =)
He he :) Good suggestion.
P.s I am not 100% sure that they try to solve exactly circular dependency issue but everything points out to it
Great content, keep it up!
Thanks, will do!
amazing videos, you don't see these topics often and are required in order to master the technology.
I never touched that advanced stuff in angular and i feel that heroes tutorial should be expanded with such topicks.
Awesome video bro 😎
Great content, Thanks !!
You are welcome 😊
Hey Dmytro, thanks for the explanation. One thing I didn't understand exactly - around 7:40, why didn't we get the 'used before declaration' error earlier when we didn't extract the provider into a separate object at the top? We're using the velocity widget component class before declaration in both the cases.
Its because compiler reads files from top to bottom. When WIDGET_PROVIDER was declared at line 5 (it doesn't matter the value of useExisting was invalid in this case) it was known to the compiler at line 13.
bloody brilliant !!
Thanks!
Hi! I have a question regarding custom providers:
Is there some way to pass an @Input() value to custom provider inside component providers: []?
Example: {provide: SOME_TOKEN, useValue: myDynamicValueFromInput}
P.S. Thank you for the video!
component providers are resolved during build, and input is resolved in runtime so no, but you can use a service for that
@@tryhuma I see, thanks!
Top!
Cool
I can't find this repository in Github. please send to me the true link. thanks dear
my problem has been solved.thanks
👍🔥💯
such a great content, so much usefull information, very good delivery, great examples, but asking to subscribe is such annoying thing, it almost kills all hard work you have done and its hard to keep watching, anyway keep it up!
Ungrateful
@@compton8301 I know, but to make good thing better someone should be "that" guy, also not asking to subscribe is a charm, and helps to people subscribe more