…list? Simple! Start by opening UserRepository: create a new public function called createIsScientistQueryBuilder(): Very simple: return $this->createQueryBuilder('user'), andWhere('user.isScientist = :isScientist') and finally, setParameter('isScientist', true): This doesn't make the query: it just returns the query builder. Over in GenusFormType, hook…

…id = some number. The only tricky part is that the andWhere() is done on the genus property - not the genus_id column: you always reference property names with Doctrine. Finish this with another andWhere('genus_note.createdAt > :recentDate') and ->setParameter('recentDate', new \DateTime(…

…we can make the argument to addIsPublishedQueryBuilder() also optional: Inside, use the new method: return $this->getOrCreateQueryBuilder() passing it $qb, and then our andWhere(): But the real beautiful thing is back up top. This whole method can now be one big chained call: return $this…

…t need any arguments, and I'm going to simplify a bit. Let's say andWhere('a.publishedAt IS NOT NULL'): You can totally see how close this is to normal SQL. You can even put OR statements inside the string, like a.publishedAt IS…

…and clicking ProgrammerRepository. Add public function createQueryBuilderForUser() with the User $user argument: Inside, return $this->createQueryBuilder() and alias the class to programmer. Then, just andWhere('programmer.user = :user') with ->setParameter('user', $user): Done! The controller passes the User to the form, and the form…

…the Homepage class. It's the same concept in Twig. And these block names - like javascripts, stylesheets and body - aren't special names... and they're not registered anywhere. Feel free to create new blocks however and whenever you want. For example, suppose we want…

…unpublished & draft - or sizes - small, medium or large - or anything similar. In the Model/ directory - though this could live anywhere... we're creating the enum for our own organization - create a new class and call it StarshipStatusEnum. As soon as I typed the word enum…

…These are called template partials... since they hold code for just part of the page. Copy this code, and in the main/ directory - though this could go anywhere - add a new file called _shipStatusAside.html.twig. Paste inside. Back in homepage.html.twig, delete that…

…to unwanted parts floating around in space - let's finish the process with a redirect. This is a classic best practice for POST forms. Let's return $this->redirectToRoute(). We can redirect anywhere, but I'll send users back to the part list for convenience…

…duplicating our autowired PHP attributes in multiple places. Super handy! Since we're not currently using that parameter anywhere except our config, we can get rid of this for now. Next: Let's see how we can autowire non-autowireable services. It's surprisingly easy.

…when it hits the database because some of the columns are null. And, we expected this! We're missing validation. Adding validation to our API is exactly like adding validation anywhere in Symfony. For example, find the name property. We need name to be required…

…create a new Message/ directory. We can put our command, or "message", classes anywhere... but this is a nice way to organize things. Create a new PHP class called AddPonkaToImage... because that describes the intent of what we want to happen: we want someone to…

…you see here is just an HTML page that I’ve loaded in my browser http://localhost:8000/index.php This is a template based on Twitter Bootstrap and it’s just a bunch of hardcoded text and links that don’t go anywhere yet…

…creates a... sort of... "shortcut". Anywhere else in this file, we can now just type SomeClassFoo: and PHP will know that we're really referring to the long class name: Acme\Tools\Foo. Or... if you leave off the as part, PHP will assume you…

…and paste that in. Since this new files lives inside the assets/ directory, we should be able to reference it publicly. Let's do that in our base layout: templates/base.html.twig. Anywhere, say , {{ and then use the normal asset() function…

…control the foreign key column: nullable: false means that every StarshipPart must belong to a Starship. So how do we say that this part belongs to this Starship? The answer is beautifully simple. Anywhere before flush(), say $part->setStarship($starship): That's it. With Doctrine…

…hard to maintain, and we won't really be able to reuse this code anywhere else. There has to be a better way to do this... and there is - with the command pattern. We can group the logic of each button into its own command…

…it's publicly available. But... nobody is using it yet. Let's try something non-traditional, but fun to start. Go into the base layout and, anywhere, say