Handling relationships within the skeleton structure about slim4-skeleton

[odan]

In my eBook I explain the Clean Architecture much more in detail.

The key point is to "think" and build software in use cases. So it's a complete "mind shift", if you will.

Here is a collection of very similar questions where you can also find some answers. I hope it helps.

• odan/slim4-tutorial#33
• odan/slim4-tutorial#32
• odan/slim4-tutorial#29
• odan/slim4-tutorial#37
• #63
• Highly COHESIVE Software Design to tame Complexity
• The ORM / Active Record Anti-pattern

[odan]

Hi @curVV

Yes, you don't need to reinvent an ORM.

The documentation of this project contains more details.
This page explains more about Repositories.

In my blog and this Slim 4 eBook you can take a deeper look at these topics. Example: Slim 4 - Cake QueryBuilder

And last but not least: If you have a specific question, you can file an issue here or consult me directly.

[curVV]

Hi, sorry I wasn't being clear. I've read the documentation and I understand how to use joins using the query builder. But it is not clear to me how to implement these relationships into the structure set out in the skeleton.

Say for instance I have a table called articles that contain articles that belong to users. If I want to implement this relationship in the current structure of the skeleton, how would you go about doing this? The UserRepository->getUserById() method returns a UserData object. Should I add a UserData->articles() method that would call something like ArticlesRepository->getArticlesbyUserId($this->id) so I could do $user->articles()? But that just means a separate query, no joins performed. That does not seem efficient to me. Trying to think of other ways...

[curVV]

Makes sense, thank you.