Chapters

18 Chapters | 1:54:58 |

01

SOLID: The Good, The Bad & The Real World

3:22
02

Single-Responsibility Principle: What is it?

7:38
03

SRP: Responsibilities

6:24
04

Refactoring for SRP

7:23
05

SRP: Takeaways

4:12
06

Open–Closed Principle

7:24
07

OCP: Autoconfiguration & tagged_iterator

4:36
08

OCP: Takeaways

5:48
09

Liskov Substitution Principle

4:19
10

Liskov: Unexpected Exceptions

6:43
11

Liskov: Substituting a Class

7:24
12

Liskov: What Changes *Are* Allowed?

7:12
13

Liskov Takeaways & Service Alias

4:54
14

Interface Segregation Principle

6:29
15

ISP: Refactoring & Takeaways

9:24
16

Dependency Inversion Principle

5:31
17

Refactoring Towards Dependency Inversion

6:53
18

DIP: Takeaways

9:22

> OOP > Write SOLID Code & Impress your Friends

Buy Access to Course

04.

Refactoring for SRP

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

8 Comments

Sort By

Login or Register to join the conversation

Jan-Makarewicz 3 months ago

Hello!
In the ~6:41 timestamp, just after copying ResendConfirmationEmailSender class from tutorial/ folder, Ryan said that he won't bother us testing that resend confirmation email, and we need to trust that it works... but, well, it seems I am this kind of rebel programmer, question all authorities ^^' and I checked that myself.. and it is not working.. right? That was merely the example to show us the SRP rule in use, but kinda incomplete (after I pasted the localhost:8000/resend-confirmation address in the Firefox, it threw 405 - Method not allowed exception (showed the error page) [Screenshot] - so as, I suppose, it should have maybe a twig template where with some "Resend email" text/button?)

I am watching it in April 2026, using php 8.3 (though, the Symfony framework, exact same as in the video - 5.2.6 (which is no longer maintained, - I know) - downloaded the code from "Downloads" and installed with Composer, as someone from your team recommended me in some other tutorial

I love the material, btw, I hope with Ryan's help I will finally learn SOLID principles, and with practice in php, within the best existing php framework! <3

|

MolloKhan SFCASTS Jan-Makarewicz 3 months ago edited

Hey @Jan-Makarewicz

I'm glad to hear you are enjoying the SOLID tutorial (it took a lot of research to write). First, about the missing test, yes, Ryan didn't write a test to save some time and keep the tutorial focused on SOLID content, but in a real app, you should at least write a functional test for your routes
Second, the 405 error, that's because the route only accepts POST requests. You navigated to that page manually, so that's equivalent to a GET request. You need to add a button somewhere and on click, submit a form with POST method.

Cheers!

1 |

theNaschkatze 3 years ago

I did all of the OOP courses in the track (until this point), but non of them explained me what is the manager folder for. I only knew services and entities... Entities store data and services do some work with the data.... but manager?

|

Victor SFCASTS theNaschkatze 3 years ago edited

Hey theNaschkatze,

Good question :) Actually, manager is a bad name to use because it really does not have much value in its name. Well, I bet people start using the "manager" suffix after Doctrine's EntityManager and so abuse this name in their own projects for their own services, but usually, there might be a better name for your services. Basically, manager is the same as service. So you can think about manager as just a service, nothing special, just a fancy name. But that's my personal opinion on it.

Cheers!

1 |

Xiro 5 years ago

on mac control+option+O
hotkey to remove unused imports

|

sadikoff Xiro 5 years ago edited

Hey Xiro

Thanks for sharing hotkey tip! It may be very useful!

Cheers!

|

Fabien 5 years ago

Why ConfirmationEmailSender is a concrete class and not an interface? Currently the caller is tied to this specific implementation and then to the specific template and synchronous mailer. Maybe I want to change the template based on the user who has just signed in, e.g. standard user, business user, gold user? Or I have recommendation links and depending on who recommended my site the template will differ (there even might not be any confirmation email for some users, and NullSender will be the way to use then)? Maybe I want to save the email in DB so a cron job will pick it up or want to send to some emails queue.
What I'm trying to say is that a caller should not care about the implementation. It should only care that it has a contract with an interface that the confirmation will be sent "somehow".

What do you think about it?

Cheers!

|

MolloKhan SFCASTS Fabien 5 years ago

Hey Fabien,

those are goods points, and if your application requires such flexibility, then, adding an interface, so you can change the implementation based on your business rules makes perfect sense, but I wouldn't add an interface to protect my code from changes that I'm not sure about. I don't like to add unnecessary abstractions which only makes more difficult to understand your code. My advice here is "keep it simple" and let changes hit you first, then, you can adapt your code and improve its design based on real things not on a guess.

Cheers!

1 |

Symfony 5.2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99.1
        "doctrine/annotations": "^1.0", // 1.12.1
        "doctrine/doctrine-bundle": "^2", // 2.3.1
        "doctrine/doctrine-migrations-bundle": "^3", // 3.1.1
        "doctrine/orm": "^2", // 2.8.4
        "knplabs/knp-time-bundle": "^1.15", // v1.16.0
        "phpdocumentor/reflection-docblock": "^5.2", // 5.2.2
        "sensio/framework-extra-bundle": "^6.0", // v6.1.2
        "symfony/console": "5.2.*", // v5.2.6
        "symfony/dotenv": "5.2.*", // v5.2.4
        "symfony/flex": "^1.9", // v1.21.6
        "symfony/form": "5.2.*", // v5.2.6
        "symfony/framework-bundle": "5.2.*", // v5.2.6
        "symfony/http-client": "5.2.*", // v5.2.6
        "symfony/mailer": "5.2.*", // v5.2.6
        "symfony/property-access": "5.2.*", // v5.2.4
        "symfony/property-info": "5.2.*", // v5.2.4
        "symfony/security-bundle": "5.2.*", // v5.2.6
        "symfony/serializer": "5.2.*", // v5.2.4
        "symfony/twig-bundle": "5.2.*", // v5.2.4
        "symfony/validator": "5.2.*", // v5.2.6
        "symfony/webpack-encore-bundle": "^1.6", // v1.11.1
        "symfony/yaml": "5.2.*", // v5.2.5
        "twig/cssinliner-extra": "^3.3", // v3.3.0
        "twig/extra-bundle": "^2.12|^3.0", // v3.3.0
        "twig/twig": "^2.12|^3.0" // v3.3.0
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.2", // 3.4.0
        "fakerphp/faker": "^1.13", // v1.14.1
        "symfony/debug-bundle": "^5.2", // v5.2.4
        "symfony/maker-bundle": "^1.13", // v1.30.2
        "symfony/monolog-bundle": "^3.0", // v3.7.0
        "symfony/stopwatch": "^5.2", // v5.2.4
        "symfony/var-dumper": "^5.2", // v5.2.6
        "symfony/web-profiler-bundle": "^5.2" // v5.2.6
    }
}

Previous Chapter

Next Chapter