We've done it! We fixed all the deprecations in our app... except for the doctrine/persistence stuff, which we don't need to worry about because we're not upgrading that library. That means... we are ready for Symfony5! How... do we actually upgrade…

…wrong. Right now, the MarkdownTransformer class has two arguments, type-hinted with MarkdownParserInterface and Cache from Doctrine: But, these are not being autowired: we're explicitly specifying each argument: If I were creating this service today, I actually wouldn't specify any configuration at first…

…But if - in our template, for example - we wanted to loop over the experts, maybe to print their names, Doctrine would be smart enough to make a SELECT statement for that data, instead of a COUNT. But that SELECT would still have the WHERE clause…

…again! Welcome back friend! In this tutorial, we're diving back into Doctrine: this time to master database relations. And to have fun of course - databases are super fun. Like usual, you should code along with me or risk 7 years of bad luck. Sorry…

…gestion des utilisateurs, tests d'acceptation et tests unitaires. Mise en place de Doctrine avec PHPUnit, pour permettre un workflow TDD hautement productif. Tester ses classes Repository avec des opérations réelles sur les données tout en conservant une vitesse fulgurante. Tester ses Entity dans le…

…users, we need to be able to run some code after API Platform deserializes the JSON into a User object, but before it gets saved to Doctrine. That code will encode the plainPassword and set it on the password property. How can we do that…

Hey friends! I mean, hello fellow space-traveling developer... friends. Welcome, to part two of our Doctrine tutorial where we talk all about... relationships. Oh, I love relationships, and there are so many beautiful types in the universe! Like, the relationship between two old friends…

…to have many Comments... and we want each Comment to belong to one Article. Forget about Doctrine for a minute: let's think about how this should look in the database. Because each Comment should belong to one article, this means that the comment table…

Let's see what this all looks like in the database! To query the user table, we can actually use the console: php bin/console doctrine:query:sql 'SELECT * FROM user' Nice! We inherited a bunch of columns from the base User class, like username…

…was probably the most important episode yet, and you made it. Congrats! The first big piece included the two main Doctrine associations: ManyToOne and ManyToMany. We saw how each can have an optional inverse side, like the OneToMany side of ManyToOne. The second huge piece…

…forms stuff and open config.yml. Under the doctrine key, we see a bunch of percent sign values: # app/config/config.yml # ... doctrine: Whenever you see something surrounded by two percent signs in a config file, it’s a parameter. Parameters are like variables: you…

…we gave every Event an owner. This was our first Doctrine relationship: a ManyToOne from Event to User. This lets us do things like call $event->getOwner(). Let’s use this to print the owner of an Event: {# src/Yoda/EventBundle/Resources/views/Event/show…

…it there: To see if it's working, try getting help information on a new doctrine:fixtures:load console task that comes from the bundle: php app/console doctrine:fixtures:load --help We see the help information, so we're ready to write some fixtures…

…we're going to take you through some of the most difficult areas of Symfony learning all about security, forms, and parts of Doctrine. We'll also see testing and learn more about how Symfony's service container works. When you get to the end…

…Postaram się pokazać jak możemy zaprojektować i wstępnie zakodować prosty przypadek rejestracji użytkownika przy użyciu TDD, a potem integrować go za pomocą Symfony Flex i Doctrina w webie. Na samym końcu postaramy się aby nasz rzypadek użycia mógł zostać wykonany asynchronicznie przy pomocy komponentu Messanger…

…If we had said no to the password question earlier, this interface wouldn't be implemented. Back in User, we see the standard Doctrine entity class attribute: ORM\Entity. We also have this ORM\UniqueConstraint attribute. This creates a unique index on the email column…

…paste some code from the tutorial/ directory. We now have three ship objects, but nothing has been saved - or persisted to the database yet. But interesting, Doctrine passes us an ObjectManager. This is the heart of Doctrine. We'll use it to save, fetch, update…

…it's a PHP class where the up() method holds the SQL to create our table. What's neat is how this was created: Doctrine compared the current state of our entities to the database and generated the SQL needed to make them match. Wow…

…s coming from Doctrine, something about raw field value access... But look at this! A link to a pull request right in the message! Very helpful, I love it! Copy the link and paste it in your browser... This is the Doctrine PR that modified…

…s a generic pagination library but has great Doctrine integration! Add the two required packages: composer require babdev/pagerfanta-bundle pagerfanta/doctrine-orm-adapter Scroll up to see what this installed. pagerfanta/doctrine-orm-adapter is the glue between Pagerfanta and Doctrine. On our homepage…