Chapters

24 Chapters | 57:23 |

01

Setup

2:10
02

Part Entity

3:12
03

Many To One: The King of Relationships

4:36
04

Setting the Relation

2:51
05

Setting Relations in Foundry

4:24
06

Fetching a Relation's Data

4:16
07

The Two Sides of a Relation: Owning vs Inverse

3:52
08

Orphan Removal

3:01
09

Ordering a Relation and "fetch" type

3:30
10

The Clever Criteria System

4:03
11

Listing Parts

2:34
12

Joining to Avoid the N+1 Trap

3:35
13

Adding a Search + the Request Object

3:54
14

Droid Entity for the ManyToMany Relationship

2:40
15

Many-To-Many Relationship

2:45
16

Setting Many To Many Relations

3:12
17

Accessing Data on a ManyToMany

2:48
18

Many To Many with Foundry

(coming soon)
19

Joining Across a Many-to-Many Relationship

(coming soon)
20

Many-to-Many but with Extra Data

(coming soon)
21

Persisting the More Complex Many-to-Many Relationship

(coming soon)
22

Hiding the Join Entity

(coming soon)
23

Re-adding addDroid(): Hide that Join Entity!

(coming soon)
24

Cascade Persist

(coming soon)

> Symfony 7 > Symfony, Doctrine Relations & Warp Drive Basics

Buy Access to Course

22.

Hiding the Join Entity

Autoplay

Lucky you! You found an early release chapter - it will be fully polished and published shortly!

This Chapter isn't quite ready...

Rest assured, the gnomes are hard at work
completing this video!

Previous Chapter

Next Chapter

Refresh the homepage and... busted! In the homepage template, we're referencing ship.droidNames. We know that this calls

$starship->getDroidNames(). But that's still trying to use the droids property that we just deleted. Let's fix that first.

Isn't It Still a Relationship between Starship and Droid?

Now, we could patch this up by looping over $ship->starshipDroids and grabbing the name off of each one. But hold up! Ignore this method for a minute. If you zoom out, this is still a relationship between Starship and Droid. So wouldn't it be nice if we could still call $ship->getDroids() and have it return a collection of Droid objects. Can it be done? Absolutely, my friend, absolutely.

Fixing the getDroids() Method

Use $this->starshipDroids->map() to transform each item in the StarshipDroid collection into a Droid object. We now have a getDroids() method that once again returns a collection of Droid objects. We rock!

Now that we have this method, down here in getDroidNames(). Instead of using the droids property, switch to the getDroids() method.

Head back to the homepage template and refresh. Success! Fetching the droids for a ship is still easy. And the rest of our code didn't need to change.

Act 5: Future-Proofing Droids

Open up the Droid entity and find getStarships(). We haven't used this method yet, but let's fix it up too. This should return a collection of Starship objects. Use the same map() trick to transform the StarshipDroid collection into a collection of Starship objects.