Affects Version/s: None
Fix Version/s: None
Component/s: Mapping Drivers
Security Level: All
This is another developer experience situation. Here is the flow:
1. I setup the owning side of a relationship (let's use ManyToMany, the hardest one for this)
2. Later, I decide to setup the inverse side of the relationship. When I do this, I of course add the `mappedBy` attribute so that it points to the exact property/relationship we're dealing with
3. Then, I also need to go back to the owning side and add `inversedBy`.
Why is step 3 (inversedBy) needed? Isn't this redundant information, since the `mappedBy` fully maps out that these 2 associations form different sides of the same relationship? I would love to remove this, I hate explaining to people starting with relationships to now go back to the main entity to add this key. It feels like duplication, which I think people sense.
Of course, I very well may be wrong and it may be needed .