Related Models about commander

[ajschmaltz]

I do still want to figure out the proper way to handle this situation, but I am now seeing that it should probably be handled within the command handler calling the repository.

[hardevine]

another option could be to have that logic in models (not every time i guess ;) )
in Post.php [model]

public static function createPost($postData, $image_ids)
{
    $post = new static($postData);
    $post->save();
    foreach ($image_ids as $image_id) {
        $post->images()->associate($image_id);
    }
}

All of this comes back to whether the code you need to add is an implementation detail or not. I like to break it down to "what is the end user actually trying to accomplish?" If the answer to that question is simply to publish a post, then I'd store the image attachment stuff within the handler.

[hardevine]

Also how to decide whether to do persistence by model ( eg.

$post->save(); 

or by repo.

$postRepo->savePost($post);

first option makes model aware of persistence implementation of framework, exception handling etc. which deviates from its purpose, also it would be handy to tackle persistence in handler if it is part of a transaction.

[bruno-barros]

I think it's a project decision. My way is always handle through repositories.

Yep - that's just an architecture decision.