💥 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
Thanks a lot for this video. I'm not a native English speaker but I was very impressed that you managed to explain the Liskov principle much better than I heard in my native language. This is because your explanation was from real life but not from books.
The Dependency Inversion Principle use case is great. The combination of local provider, Injection Token, useExisting and Content Projection is just epic. Good job Dmytro!
5:04 if you're not good at listening English (not your native language) like me, and has a little trouble to get what rule he said, it's the "And rule" (the auto caption generates "end", and I took some time to figure it out)
Thank you! Very helpful. It is quite challenging to find such a good combination of integrity, consistency and practicality inside one video about Angular. Definitely favorite frontend youtube channel!
Not sure about Open/Close principle. For me your explanation looks more related to code reusability. I expected smth more parent - child (when child class extends parent) related examples. What do you think? But explanations of other principles are amazing)
I really 🤍🤍🤍🤍🤍🤍 u .You rescue me today in the interview.Your video before the interview with 2 hours makes solid very clear.Allah bless u .Keep do this please apply head first design pattern in angular also 🤍🤍🤍🤍 u from Egypt.
Great content! Congratulations 👏👏 Would be great if you create a video about debugging angular memory leaks. 😉 it's an difficult issue to find good references.
How to do Component communication as it becomes much harder when working with multiple sub components. Especially, getting data in the parent component.
This contains video invaluable information. Thank you very much for putting the time and effort creating this. The example is fantastic with the right mount of complexity to deliver the learning lesson. Thank a lot. Keep it up. I really like the content you are making.
Hey Dmytro, Just a thought that we can mark properties optional in interfaces in that way we need not to make multiple interfaces. What are you guys think about it???
Thanks a lot, Dmytro! I might have some recommendations for you. I hope It would be great if you describe or explain and show your little padawan's the right way of use. 1 - Observables 2 - HostListeners. Thanks a lot!
A little side note for the Interface Segregation Principle, since it has a major benefit that maybe isn't clear in the beginning: The angular lifecycle hooks are a great example since every hook method has its own interface. The benefit of the principle is that a) implementation developers do not need to implement irrelevant code (as demonstrated in the video) and b) implementation developers of your library/component whatever will only ever see those bits of the implemented code that is relevant to them when you provide them references to classes. b is maybe not so obvious but imagine you had a class that has some methods that must be public due to other internal dependencies (the way component classes are forced to have public props/methods for their template immediately comes to mind) but you don't necessarily want the implementation developers that use your class see all the methods. The solution is to write an interface and only ever provide variables to the class typed with that interface. That could be in callback Methods, abstract methods or anywhere else where an instance to a consumable class would occur. This pattern is especially useful in typescript where you have so many different ways to compose your classes due to the nature of javascript. Example: You have an API abstraction with read and write methods (yes that sort of breaks CQRS, but let's ignore that) but you want to expose only the reader API although all operations are implemented in one class. That's where you would expose the class instance by typing it with the IReader (silly name, sorry) interface. Consumer code can now only access the reader methods. Unless they (apiInstance as IWriter).write :D
At about the example with di and services. If we inject the service, even if Angular substitutes its token. If we then need to replace the service with another and remove it, then we will not be able to do it, right? Because it is used as an interface Isn't that a problem? In a traditional OOP, we simply create an abstract class, or interface, and inject it. Therefore, we can dynamically change services if they implement an interface. But if in Angular service = interface, then we can do so only by replacing service statically?Like using "useExisting"
I have the same problem now. I'm trying to understand the OOP principles and their patterns, but it's still hard to see them in Angular. And if you can find examples of principles, it is more difficult with specific patterns, because you read mainly on examples of object-oriented languages, where only one paradigm, and we have OOP, Functional programming, Reactive programming. And you just ask yourself "The problem is that I do not find them yet, or we just do not have them in JS/TS"
Have you thought about making some series about jasmine and tests in Angular? I would be happy to see it on your channel. You do great, keep it like this.
Hi, i have one question :) What is aan impact to bundle size creating multimple components, services in single responsibilyty principle? It's ok to split logic as match as possible is any impact on bundle size? :)
Hi! Well, Theoretically your bundle size may obtain few additional bytes if you had a large app but it is incomparable with benefits in maintaining the code base that follows SRP :)
Great explanation as always! About DIP do you use injection token for multiple optional interfaces? Say weather implents reloadable, unitConversion and velocity implements unitConversion only. And parent component should be able to distinguish child capabilities and disable conversion, reload button accordingly.
Can you please make a another video for ng-content and ng-template . Like what is use case where we must use ng-content or ng-template . Like I know the one diff we can pass data from container to template but I want to know this in more details. Please help Thanks In advance.
@@DecodedFrontend Thanks for this video its very informative...few months back I was searching SOLID principles using angular, today got a proper video with very nice explanation 👍
Good content as usual bro, I like it. ♥ Just I wanna mention your little typo that "wether" must be "weather" :D Anyways,, keep posting such nice videos
Another excellent video, Dmytro. Thank you for educating me on the use cases where SOLID could be used with Angular. I will have to re-watch that last Dependency Inversion section a few more times to understand better. Nevertheless, the 40 minutes taken up in this video flew by with so much knowledge you shared. Thank you for being awesome!
💥 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
Thanks a lot for this video. I'm not a native English speaker but I was very impressed that you managed to explain the Liskov principle much better than I heard in my native language. This is because your explanation was from real life but not from books.
The Dependency Inversion Principle use case is great.
The combination of local provider, Injection Token, useExisting and Content Projection is just epic.
Good job Dmytro!
Thanks Adrian! ;)
hejka
5:04 if you're not good at listening English (not your native language) like me, and has a little trouble to get what rule he said, it's the "And rule" (the auto caption generates "end", and I took some time to figure it out)
Thank you Phuc! 🙏🏻 indeed I meant “And-Word-Rule“. Sorry for inconvenience, I have fixed the subtitle 😊
You're welcome 😊
Thank you! Very helpful. It is quite challenging to find such a good combination of integrity, consistency and practicality inside one video about Angular. Definitely favorite frontend youtube channel!
This content is really really awesome
Just asking which extension you are using for creating component
Thank you! The extension is called NX Console
Your channel is handsdown the best Angular channel on TH-cam, many thanks!
This is very rich content, thanks for sharing it across.
Awesome video, what is the name of the extension your using for generating the component?
Hi, it is called “NX console” :)
Was looking for an angular related channel and this is noice, well explained and good stuff. Thank you
Thank you so much. This is all I've been searching for months.
Admirable your comprehension of Angular, thanks god i found your channel, thank you teacher.
I was looking for something like this. Is kind of hard to understand this concepts but with easy examples as you showed, is just simple ! thanks
Thank you for your feedback 😊 glad you liked it!
Not sure about Open/Close principle. For me your explanation looks more related to code reusability. I expected smth more parent - child (when child class extends parent) related examples. What do you think?
But explanations of other principles are amazing)
Definitely you have to be mentioned in the Angular documentation!
As always, another useful video on your useful YTchannel !
Make a pull request adding the link!
True. Even Angular Team will know some new concepts 😆
Not gonna lie, i didn't think i'd learn anything here, but damn the DI Principle was partly new to me. Thumbs Up, thank you for showing me that!
Does anybody knows what is the name of VSCode extension for colorized offsets in CSS and HTML templates?
P.S. Thanks for the video, Dmytro!
Finally New Video 😊
it's the most impressive video on frontend topic! huge and unique content, thank you a lot!
You have made my day!
Thanks a lot.
Cheers from Tbilisi✊🏻
Thanks! Happy to hear that 😉
Hello, Dmitry!
Could you please add more design pattern videos in context of Angular?
I find your approach extremely useful to understand
Great Video, Loved It ❤, BTW Which extention are you using to generate components.
Hi! Thank you! I use ext called nx console marketplace.visualstudio.com/items?itemName=nrwl.angular-console
@@DecodedFrontend thank you very much, I appreciate it 👍👍
Amazing video, Dmytro. Do you intend to continue this serie? Talking about architecture styles in Angular, such as CleanArch, will be great.😃
Thanks for the idea, Paulo!
What a great class 👏, I would like to know more about how we can abstract logic everywhere to have a code as clean as possible
I really 🤍🤍🤍🤍🤍🤍 u .You rescue me today in the interview.Your video before the interview with 2 hours makes solid very clear.Allah bless u .Keep do this please apply head first design pattern in angular also 🤍🤍🤍🤍 u from Egypt.
Glad to hear that, Aya! Good luck with your new job ;) P.s sorry for the late reply
Great content! Congratulations 👏👏
Would be great if you create a video about debugging angular memory leaks. 😉 it's an difficult issue to find good references.
Great suggestion! Thank you 😊
Make a video on takeUntil of RxJS Subject which can help reduce memory leaks while using observables.
So Thankful for this Video
This is brilliant content. Beautifully expalined.
That was awesome, you won a new susbcriber, thank forr share
You are welcome! Thanks for sub🙂
Hi Dmytro, which extension are you using to create new components? Looks good option to CLI, thanks
It is NX Console - ext for vs code
How to do Component communication as it becomes much harder when working with multiple sub components. Especially, getting data in the parent component.
This was great. Thanks for putting this together!
Excellent tutorial! Earned a sub :)
As always, thank you for quality materials. Gonna check it yout later :)
Pls explain how to make reusable angular tabs as shared or child components.. that should open components dynamically
Thank you, Dmytro. I love you man. 👍👍👍👍
😀 👍
This contains video invaluable information.
Thank you very much for putting the time and effort creating this.
The example is fantastic with the right mount of complexity to deliver the learning lesson.
Thank a lot. Keep it up. I really like the content you are making.
Very great examples. I think best I've seen so far. Thanks!
You're genius !! Thank you for sharing your knowledge with us :)
really good examples thanks. specially for DI
Thanks you have explained this difficult subject in a way that makes it digestible.
Гуд ту кноу, дуже дякую 🙃
All explained very well specially dependency inversion principle. 🙏🙏👌👌
like before watching ... as always
Excellent explanation. Thank you
Great video.
Just like to know how to integrate git in vscode just like you?
Hey Dmytro, Just a thought that we can mark properties optional in interfaces in that way we need not to make multiple interfaces. What are you guys think about it???
Thanks a lot, Dmytro! I might have some recommendations for you. I hope It would be great if you describe or explain and show your little padawan's the right way of use.
1 - Observables
2 - HostListeners.
Thanks a lot!
Can you share what extension you're using for those nice block color highlights? Thanks!
Good content. I am watching in 2x and it feels normal. 😊
A little side note for the Interface Segregation Principle, since it has a major benefit that maybe isn't clear in the beginning:
The angular lifecycle hooks are a great example since every hook method has its own interface. The benefit of the principle is that
a) implementation developers do not need to implement irrelevant code (as demonstrated in the video)
and b) implementation developers of your library/component whatever will only ever see those bits of the implemented code that is relevant to them when you provide them references to classes.
b is maybe not so obvious but imagine you had a class that has some methods that must be public due to other internal dependencies (the way component classes are forced to have public props/methods for their template immediately comes to mind) but you don't necessarily want the implementation developers that use your class see all the methods. The solution is to write an interface and only ever provide variables to the class typed with that interface. That could be in callback Methods, abstract methods or anywhere else where an instance to a consumable class would occur.
This pattern is especially useful in typescript where you have so many different ways to compose your classes due to the nature of javascript.
Example: You have an API abstraction with read and write methods (yes that sort of breaks CQRS, but let's ignore that) but you want to expose only the reader API although all operations are implemented in one class. That's where you would expose the class instance by typing it with the IReader (silly name, sorry) interface. Consumer code can now only access the reader methods. Unless they (apiInstance as IWriter).write :D
Отличное видео! Лучшее из тех что я видел на эту тему. Лайк и подписка!
Fantastic topic! Thanks a lot! 👌
Tell about your glasses ,, Where do u get them and which is best for developers ?
Super cool content... Thanks, I am glad that I came across your channel 🙏
Can you do a video on unit testing long poll with Rxjs using timer, switchmap and takeuntil?
What would I say?
- It was so fuc**ng gooood))) Thx a lot)
Thanks a looot 🤘🏻😉
Hi
can you also create a video on how we can create micro frontends.
Thank you Dmytro! I love your videos. You are gifted, clear and short explanation, easy to follow. Thank you 🙏
One of the best exemple of SOLID in real-life Thank you! The last DI exemple was confusing tho :)
At about the example with di and services. If we inject the service, even if Angular substitutes its token. If we then need to replace the service with another and remove it, then we will not be able to do it, right? Because it is used as an interface
Isn't that a problem?
In a traditional OOP, we simply create an abstract class, or interface, and inject it. Therefore, we can dynamically change services if they implement an interface. But if in Angular service = interface, then we can do so only by replacing service statically?Like using "useExisting"
Do you have any video which talks about Replaysubject() in RxJs ?
Can you please list out the VS Code plugins you are using?
Hi, What extension do you use for generate a class?
Great explanation. Thanks 👍🏼
You're welcome! :)
Excellent content!
Glad you enjoyed it
Awesome stuff
hi Dmytro, thanks for sharing great content - very informative and easy to follow/grasp thanks to your teaching style.
I have the same problem now.
I'm trying to understand the OOP principles and their patterns, but it's still hard to see them in Angular.
And if you can find examples of principles, it is more difficult with specific patterns, because you read mainly on examples of object-oriented languages, where only one paradigm, and we have OOP, Functional programming, Reactive programming. And you just ask yourself "The problem is that I do not find them yet, or we just do not have them in JS/TS"
Thanks guy 😀🤝
My pleasure 🙂
You right: splitting by extremely small pieces is overkill
Hi Dmytro, which extension are you using that shows file size on the top? Thanks
Hi! This is an extension called Import Cost marketplace.visualstudio.com/items?itemName=wix.vscode-import-cost
@@DecodedFrontend Thanks again!
Have you thought about making some series about jasmine and tests in Angular? I would be happy to see it on your channel. You do great, keep it like this.
Why Jasmine? Jest most probably
Hi, i have one question :) What is aan impact to bundle size creating multimple components, services in single responsibilyty principle? It's ok to split logic as match as possible is any impact on bundle size? :)
Hi! Well, Theoretically your bundle size may obtain few additional bytes if you had a large app but it is incomparable with benefits in maintaining the code base that follows SRP :)
Thanks for making this video. Thank you 😊😊👍❤
how to maintain single responsibility in case u need to show the user pre-selected values in the dropdown?
Rally cool! Thanks
Great to hear that! Thanks :)
One class file doing HTML, CSS and JS? Im sure you kept it together for ease of showing, but that itself breaks SRP.
Great explanation as always! About DIP do you use injection token for multiple optional interfaces? Say weather implents reloadable, unitConversion and velocity implements unitConversion only. And parent component should be able to distinguish child capabilities and disable conversion, reload button accordingly.
Hi Piotr! Thank you for feedback!
If I encountered such a use-case I would go most probably with multiple tokens (each for every interface).
@@DecodedFrontend and then provide same 'existing' class for both?
If by 'existing' you mean useExisting than yes :)
@@DecodedFrontend yes that is what meant ;)
Any plan to create a tutorial on server side rendering in angular
Can you please make a another video for ng-content and ng-template . Like what is use case where we must use ng-content or ng-template .
Like I know the one diff we can pass data from container to template but I want to know this in more details. Please help
Thanks In advance.
Would you consider mixing Generics into these examples? Do you use Generics?
Awesome tutorial! 👍
awesome stuff.
what is the name of extension he is using to generate components any idea ?
Hi,
Thanks for this good stuff. Can you please make a tutorial on view encapsulation and change detection?
Loved it!
Advanced content, thanks
You’re welcome ☺️
What is this VS Code extension used in this video to run ng commands interactively?
Last one is bridge pattern right?
Exactly :) This design pattern actually implements at least 2 design principles: Dependency inversion and Open/Closed principle
@@DecodedFrontend Thanks for this video its very informative...few months back I was searching SOLID principles using angular, today got a proper video with very nice explanation 👍
very nice, thank you!
Pls create angular ecommerce app will material and latest concept.. there is a very less tuts on angular..
Nice, Thanks!!!
Nice video. Thanks for sharing your knowledge.
Just one word, legend
Can you do an video of Module Federation implementation in Angular 12 which has webpack 5.
Excellent video. Thank you. Could you please do a video on ngTemplateOutlet?
Good content as usual bro, I like it. ♥
Just I wanna mention your little typo that "wether" must be "weather" :D
Anyways,, keep posting such nice videos
ah... Indeed, you're right :)
Sir, all coding principle and coding standards rules
Another excellent video, Dmytro. Thank you for educating me on the use cases where SOLID could be used with Angular. I will have to re-watch that last Dependency Inversion section a few more times to understand better. Nevertheless, the 40 minutes taken up in this video flew by with so much knowledge you shared. Thank you for being awesome!
Thanks a lot for your feedback, Guillermo! Much appreciated :)