- Видео 2
- Просмотров 9 829
Taylor Daughtry
США
Добавлен 22 сен 2012
SOLID Principles in Laravel & PHP: A Practical Guide
If you've been seeking clarity on making your PHP applications more maintainable, scalable, and robust, then this guide is for you.
This video covers:
- **Single Responsibility Principle (SRP)**: Keeping your Laravel controllers and models focused.
- **Open/Closed Principle (OCP)**: Enhancing features without touching old code.
- **Liskov Substitution Principle (LSP)**: Ensuring interchangeable objects in PHP for less breakable code
- **Interface Segregation Principle (ISP)**: Designing lean, purposeful interfaces for your Laravel applications.
- **Dependency Inversion Principle (DIP)**: Inverting control for better application structure, shorter files, and better testing.
**Timestamps:**
00:00 -...
This video covers:
- **Single Responsibility Principle (SRP)**: Keeping your Laravel controllers and models focused.
- **Open/Closed Principle (OCP)**: Enhancing features without touching old code.
- **Liskov Substitution Principle (LSP)**: Ensuring interchangeable objects in PHP for less breakable code
- **Interface Segregation Principle (ISP)**: Designing lean, purposeful interfaces for your Laravel applications.
- **Dependency Inversion Principle (DIP)**: Inverting control for better application structure, shorter files, and better testing.
**Timestamps:**
00:00 -...
Просмотров: 8 712
Видео
Route Model Binding | Five Minute Laravel
Просмотров 1,1 тыс.6 лет назад
Route Model Binding is a handy feature of Laravel that makes our lives as developers easier. We don't have to think about it-Laravel just makes it happen automatically. And if you've used Laravel for longer than a few days, you've probably used route model binding before-but there are a few things hiding in the documentation that might come in handy for your next project-like Explicit Binding! ...
I can't tell you how disappointing it is to find such a clear and thorough video aimed at programmers working actively in PHP / Laravel to then find out you don't have other videos on your channel…
Thanks for laying this out so clearly. The whole time you were going over the Liskov Substitution Principle I was expecting you to suggest type-hinting the array structure using DocBlock and static analysis tools! That's what our team uses to enforce this programmatically.
Thank you sir.. I gained knowledge and tricks here. I will work more on understanding and adhere to SOLID principle
Thanks 🙏
SOLID video 🤘
Hey Taylor, are you looking for a job as a laravel dev? If yes, any way to contact you?
i got error using the same logic. The purchase method is confusing in Open/Closed Principle
yeah me too
Thank you for the great video on SOLID. Please do more videos.
Great explanation. Subscribed!
the things that i noticed sometimes with the way laravel is built is that sometimes added too much extra abstractization ends up making spaghetti code
Quality content. Subscribed! You mentioned you have a strong opinion on the repository pattern; do you have any video or article outlining your opinions?
Just a minor correction. The D in solid refers to Dependency Inversion. But yes, you're correct that it means that you should depend upon abstractions rather than concretions. Great video :)
developer))) there is no such principle as dependency injection there is dependency inversion principle ruclips.net/video/nL7jpo1YsyU/видео.html Laravel gives birth to noobs
Nice video. Any plan for more education videos like this in future?
Nice video, you should make more, great teaching style, cheers 👊🏾
That's one of the best explanations of SOLID I've seen in a long time. Maybe it's because the examples were created using a familiar environment, but regardless, good job!
For SRP validation should be done in the productService as well. That is business logic and not related to the HTTP cycle.
There's input validation and there's business-related validation. Limiting the string length, ensuring price is numeric, or restricting the image size is typically not part of the business logic.
that's why you have the request classes, for validation
This was a great breakdown and one that I would love to share with my dev team.
Straight to the point and no bullshit with showing us the useless behind the scene stuff that didn't matter! Excellent video! Should do just small ones like this.
Nice Video , Clear Video!
Thanks! :D