Nicolas PHILIPPE
Nicolas PHILIPPE
hi! I'm closing this stale issue. Don't hesitate to reopen it!
do you have any problems with dama?
> But how do you keep those subtree splits updated, and how/where will you tag releases when the different parts evolve at a different pace? what Symfony does is to...
> PhpStorm does not yet understand it I've tried your PR, and trying to "ctrl + click" `createMany()` in this code, and it works pretty well ```php // \Zenstruck\Foundry\Tests\Functional\RepositoryProxyTest public...
if PHPStorm does not understand it, we could change like this, maybe? ```php /** @return class-string */ abstract protected function categoryClass(): string; /** @return class-string */ abstract protected function categoryFactoryClass():...
thanks for you answer! I think this may be the way to go, but... `Comment::$post` is mandatory is the db... so how could I tell foundry to hydrate it somehow?
Hello @kbond sorry, I have not seen the notification. This is indeed my problem. But how could we be sure the original `Post` entity created will be the one used...
something simple such as ```php public function addComment(Comment $comment): self { if (!$this->comments->contains($comment)) { $this->comments->add($comment); } return $this; } ```
This could happen, indeed
Hi @1ed I think you raise a fair point here. IMO the cleanest way to handle this would be to split the Instantiator and to introduce something like an `Hydrator`....