SOLID Design Principles in
Vložit
- čas přidán 27. 07. 2024
- 🔥 Learn how to build really complex Angular forms & form controls with my new advanced course bit.ly/advanced-angular-forms 🔥
Use coupon: CZcams_DISCOUNT to get -a 10%-off discount!
I am quite sure that every one of you has heard about S.O.L.I.D design principles which help to design our code maintainable and flexible. In this video, I wanted to show you how these principles could be applied to your Angular applications. I hope you will find something useful and enjoy watching it!
⭐ Successful Interview "Angular Interview Hacking" course
courses.decodedfrontend.io/co...
⭐ Become a Pro in Angular Material Theming
bit.ly/angular-material-themi...
⭐ Blazing fast GraphQL Backend just in 1 Day with Hasura Engine
bit.ly/complete-hasura-course
00:00:00 - Intro;
00:01:05 - What is Design Principle;
00:02:23 - Single Responsibility Principle;
00:13:21 - Open/Closed Principle;
00:21:40 - Liskov Substitution Principle;
00:27:15 - Interface Segregation Principle;
00:32:52 - Dependency Inversion Principle;
00:41:02 - Outro;
🔗 Link to the source code on GitHub:
github.com/DMezhenskyi/solid-...
#webdevelopment #angulartip #frontend - Věda a technologie
💥 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
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!
Thank you so much. This is all I've been searching for months.
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
Your channel is handsdown the best Angular channel on CZcams, many thanks!
Thank you Dmytro! I love your videos. You are gifted, clear and short explanation, easy to follow. Thank you 🙏
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.
Was looking for an angular related channel and this is noice, well explained and good stuff. Thank you
This is very rich content, thanks for sharing it across.
hi Dmytro, thanks for sharing great content - very informative and easy to follow/grasp thanks to your teaching style.
Very great examples. I think best I've seen so far. Thanks!
Admirable your comprehension of Angular, thanks god i found your channel, thank you teacher.
This was great. Thanks for putting this together!
As always, thank you for quality materials. Gonna check it yout later :)
You have made my day!
Thanks a lot.
Cheers from Tbilisi✊🏻
Thanks! Happy to hear that 😉
Thanks you have explained this difficult subject in a way that makes it digestible.
Fantastic topic! Thanks a lot! 👌
Super cool content... Thanks, I am glad that I came across your channel 🙏
Finally New Video 😊
Awesome stuff
it's the most impressive video on frontend topic! huge and unique content, thank you a lot!
Excellent explanation. Thank you
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.
So Thankful for this Video
This is brilliant content. Beautifully expalined.
awesome stuff.
Thank you! So amazing video!
really good examples thanks. specially for DI
Thanks for making this video. Thank you 😊😊👍❤
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 :)
Nice video. Thanks for sharing your knowledge.
Отличное видео! Лучшее из тех что я видел на эту тему. Лайк и подписка!
very nice, thank you!
Excellent tutorial! Earned a sub :)
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!
Awesome tutorial! 👍
Loved it!
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!
Excellent video, thank you!
Glad it was helpful!
like before watching ... as always
Greate Content !!
Thank You So Much For This Video...
That was awesome, you won a new susbcriber, thank forr share
You are welcome! Thanks for sub🙂
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 😆
Гуд ту кноу, дуже дякую 🙃
Thank you!!
All explained very well specially dependency inversion principle. 🙏🙏👌👌
Great explanation. Thanks 👍🏼
You're welcome! :)
Thank you, Dmytro. I love you man. 👍👍👍👍
😀 👍
Amazing!
Nice, Thanks!!!
Great channel!
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!
Hi Dmytro, thank you for all that interesting topics that you covered so far. The way that you are explaining everything in deep is very very good approach and again than you for that. Can I give you an idea to explain the change detection strategy more deeply with couple of examples, thanks in advance ;)
Nice as always..
Good content. I am watching in 2x and it feels normal. 😊
Great video
Thanks guy 😀🤝
My pleasure 🙂
Excellent content!
Glad you enjoyed 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!
Thank you !!!
You are the best
One of the best exemple of SOLID in real-life Thank you! The last DI exemple was confusing tho :)
Rally cool! Thanks
Great to hear that! Thanks :)
Thanks!
Just one word, legend
Hello, Dmitry!
Could you please add more design pattern videos in context of Angular?
I find your approach extremely useful to understand
Hi,
Thanks for this good stuff. Can you please make a tutorial on view encapsulation and change detection?
Advanced content, thanks
You’re welcome ☺️
You are indeed the Angular Papa
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
good job
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.
Excellent video. Thank you. Could you please do a video on ngTemplateOutlet?
You're awesome.
Glad to be useful 😊
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!
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
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)
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
You right: splitting by extremely small pieces is overkill
SICK. hell yea
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
Just best.
Hi
can you also create a video on how we can create micro frontends.
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 😊
Pls explain how to make reusable angular tabs as shared or child components.. that should open components dynamically
What would I say?
- It was so fuc**ng gooood))) Thx a lot)
Thanks a looot 🤘🏻😉
Awesome video, what is the name of the extension your using for generating the component?
Hi, it is called “NX console” :)
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 :)
Great video.
Just like to know how to integrate git in vscode just like you?
Can you share what extension you're using for those nice block color highlights? Thanks!
great
This content is really really awesome
Just asking which extension you are using for creating component
Thank you! The extension is called NX Console
Can you do a video on unit testing long poll with Rxjs using timer, switchmap and takeuntil?
nice
Can you do an video of Module Federation implementation in Angular 12 which has webpack 5.
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???
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 👍👍
Do you have any video which talks about Replaysubject() in RxJs ?
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"