Foundry Tricks

It's a static method now: QuestionFactory::createMany(30); will work.

Hey Adrian,

Yes, it should be possible! Hm, probably you forgot a return statement in one of your methods, e.g. in unpublished() or unready() - it's the most comment error I think. Otherwise, it would be good to see an error if you have any.

Cheers!

That's was that ! Sorry for useless question ! Thanks you for your answer

Hey Adrien,

No problem, that's easy to miss ;) I'm happy to hear it works for you know!

Cheers!

Hey Pieter-jan C.

Good catch. Thanks for your report we will add a note about it.

Cheers!

Hi Mathias!

First, I'll say that I don't use references anymore. I just put everything into a single fixtures class and don't bother with them. Even if I did want to split my fixtures into multiple classes, I might just query for the objects I'm looking for. Or use foundry to find random items - e.g.

ProductFactory::createOne([
    'category' => CategoryFactory::random()
]);

But, to answer your question.... yes and no! :p. The answer is no. But, that's actually by design. With Foundry, you are still using DoctrineFixturesBundle to actually load your fixtures. So you can continue to use its reference system. It might be something like:

$product = ProductFactory::createOne();
// calling ->object() so you can "unwrap" the object and get the real one (Foundry gives you back a "proxy" object initially)
$this->setReference('key', $product->object());

Let me know if this helps :)

Cheers!

Hi Ryan,

thanks for your help. I tried your examples and ran into some problems.

I understand your thoughts and examples beyond. In my case I'm using fixtures (especially DependentFixtures) for loading roles of user into the database. After I changed RoleFixture by using the factory of Foundry, I had add trait of ResetDatabase and Factories to the fixture-tests, because a single RoleFactory call had some problems with $entitymanager->flush(). After adding the traits my test-code was running very slowly and interrupted. So I stopped my experiment with Foundry on UnitTests.

In my next step I want to use Foundry for building up a dev-environment on a test stage.

Cheers!

Hey Mathias!

I'm using fixtures (especially DependentFixtures) for loading roles of user into the database. After I changed RoleFixture by using the factory of Foundry...

Yes, I agree: I think the mixture of the DependentFixtures system and Foundry won't play nicely together. So if you're heavily dependent on DependentFixtures, stay with that. But eventually, using Foundry would be nice :). They have a "stories" feature where you can pre-define "Sets" of fixtures and load them very easily: https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#stories

Cheers!

Howdy!

Yes, but not directly. If we have:

#[ORM\Entity(repositoryClass: UserRepository::class)]
#[ORM\Table(name: '`user`')]
class User
{
    #[ORM\Column(length: 255)]
    private ?string $name = null;

    #[ORM\Embedded(class: Address::class)]
    private Address $address;
    
    public function __construct()
    {
        $this->address = new Address();
    }
    
...
}

And

#[ORM\Embeddable]
class Address
{
    #[ORM\Column]
    private string $city;

    #[ORM\Column]
    private string $state;
...
}

We can run bin/console make:factory selecting User and MakerBundle will generate a factory that looks like:

final class UserFactory extends ModelFactory
{
    protected function getDefaults(): array
    {
        return [
            'name' => self::faker()->text(),
            'address.city' => self::faker()->text(),
            'address.state' => self::faker()->text(),
        ];
    }

    protected static function getClass(): string
    {
        return User::class;
    }
}

They key thing is your User class needs to have a getter and setter for User::address and Address of course needs getters/setters for it's respective properties.

Then you just use foundry as you would with any other entity. E.g. $users = UserFactory::createMany(5);

Hey Pawel,

Do you get an error, or just the locale is not changing? If it's the latter, try clearing the cache manually rm -rf var/cache

Cheers!

Hey MolloKhan,
Thank for your reply.
I cleared cache, resutl is better, two or 3 my entieties has now data in en_US, but one has still Latin names.

    protected function getDefaults(): array
    {
        return [
            // TODO add your default values here (https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#model-factories)
            'Name' => self::faker()->text(20),
        ];
    }

My method getDefaults looks for Category and GoalTypes looks like above, but no idea, why they give different results.
I just try to create new project, but after
download https://bitbucket.org/pawelwaw/test/downloads/pawelwaw-seventagen-d894536c507f.zip
`composer install `

and

doctrine:migrations:migrate

command
doctrine:fixutures:load

still give me latin texts. Maybe you can try on your machine.

I finally found out why this happen.

'Name' => self::faker()->text(20),

method text use finally method word this is not supported internationaliration and call Lorem.php class insted of Text Class from configured Provider Class, So I suppose I should add myself class Lorem which will extends Base Lorem class.
Or as I decided get word form realText function

    protected function getDefaults(): array
    {
        preg_match('/(?P<name>(\w+){8,10})/', self::faker()->realText(100), $matches);
        return [
            'Name' => $matches[0],
        ];
    }

Ohh, that's interesting and makes sense, the text generator was not going through the translation process. I'm not sure if that's on purpose or just a bug on the bundle

Hey Gizmola!

Thanks for posting the solution to the issues you got - and I'm sorry you hit them!

> I started this series with symfony 5.0 and php 7.3

yea, I can't remember exactly why, but PHP 7.4 is the minimum version we have marked for this tutorial. Some things may work on php 7.3 (as you saw), but it gets "iffy" since we haven't tested with it.

> I don't know if symfony/string is now included by default, but I thought this might bite someone else.

That's actually a good point. In the tutorial code, it IS installed because both symfony/console 5.2 and symfony/property info 5.2 (both of which we have installed) requires it. But with a version of Symfony 5.1 or before, you wouldn't have it. That would have been a good thing for me to mention :).

Cheers!

Hey davidmintz

I think you can tweak your relation to CASCADE remove objects, that will drop all related objects with parent one, and purging will work from the box.

Ping me back if it works ;)

Cheers!

Yay! Thank you!

We have a Person entity and its subclass Patient, organized by way of Single Table Inheritance (seems like a reasonable choice for my case). A Patient sometimes has a Payer, but usually not (we're gonna bill the Patient, not someone else, and the rest is their problem. Yeah this is the USA where the healthcare system itself is terminally ill). So the Patient's "payer" property is in a unidirectional OneToMany relation with Person. I had an issue Integrity constraint violation: 1451 Cannot delete or update a parent row... with purging as described above. Adding the following annotation solved it:

/**
 * @ORM\ManyToOne(targetEntity=Person::class)
 * <b>@ORM\JoinColumn(name="payer_id",onDelete="SET NULL")</b>
 */
private $payer;```

Yo! Thanks for the reply, and I'm happy that my answer get you closer to solving issue =)

Cheers and stay safe!

Hey MattHB!

Yep, that's totally true if you add types to your properties and don't initialize them. So, your fix is definitely 👍. Alternatively, you can default $slug to null:

private ?string $slug = null;

Cheers!

Hey @Rob!

Hmm, I see what you're saying! Ok, let's look at the two sides of this:

1) When you use dateTimeBetween from Faker - https://fakerphp.github.io/formatters/date-and-time/#datetimebetween - that does give you a DateTime object. As far as I can see, there is no way currently to opt into a DateTimeImmutable. But, that's ok! (see my next point)

2) The error is being caused because the setAskedAt() method in your entity has a DateTimeImmutable type-hint on it. If you check, the method probably looks like this:

public function setAskedAt(?\DateTimeImmutable $askedAt)
{
    // ....
}

Fortunately, this is YOUR code to change. I think changing it to a \DateTimeInterface would work fine, as DateTime objects implement this :). I just checked the "finished" code from our tutorial, and it does use DateTimeInterface - here is exactly how the method looks:

public function setAskedAt(?\DateTimeInterface $askedAt): self
{
    $this->askedAt = $askedAt;

    return $this;
}

My guess is that you selected the datetime_immutable option when using the make:entity command, which uses this type-hint. If you did this on purpose... that's valid but... well, unfortunately, it doesn't look like the dateTimeBetween() plays nicely with this.

Cheers!

Hey somecallmetim!

Yea, sorry about the big delay - we've been busy with a bunch of frontend stuff (Stimulus, Turbo), which I know a lot of people LOVE... but also a lot of people want this stuff too :).

> Authentication and generating fixtures with relationships are things I would really love to have tutorials on

These are the next two that will happen in this series (probably relations first... so we have more to play with for Authentication). I was waiting for Symfony 5.3 for authentication, as it has some nice changes - and Symfony 5.3 will be released in about 2 weeks. Overall, my guess is that the next parts of this series will be at least 1 month away (the Turbo tutorial is in front of it).

However, if you have any specific Foundry questions or problems, feel free to ask them here! That might help me know what things we should talk about with it... or even ways to improve the Foundry docs (I talk frequently with its author).

Cheers!

Hey m3tal!

Hmm. Do you happen to have any cascade={"persist"} on any of your Doctrine annotations for the relationships? Also, could you pass the stack trace of the error (if you don't see it in the terminal, you can add -vvv when you run the command to get it). Finally, if you could post the relevant entity code (the related properties, ManyToOne/OneToMany annotations, and the getDefaults() of your factory classes), that would help :).

Overall, I don't see any problem from the code you've posted - so we need to dig deeper :).

Cheers!

Hi.
Kevin, your friend, give me the workaround.
Here's

ProductFactory::new()->createMany(50,[
    'productOptions'=>ProductOptionsFactory::new([
        'productExtra'=>ProductExtrasFactory::new()->many(10)
    ])->many(5)
]);

thanks Kevin Bond.

Woo! He's the best! Thanks for sharing the solution here! I should have seen that my self to be honest - I'm glad Kevin did!

seems like it is overwriting it, once I have changed __construct(User $user123) it seems to be working

Hey Peter,

Hm, fairly speaking I don't know, I would suppose it should work with "User $user" argument name as well, or probably it's a bug that might be already be fixed in the latest version of that bundle, or probably it's a known limitation of this bundle. Anyway, thank you for sharing your solution with others!

Cheers!

Hey <blockquote></blockquote>Peter K.!

Excellent question!

This was working but is there any way to define those arrays in CarFactory class so I wont be messy if I will keep it in AppFixtures?

I think what you're looking for our "stories": https://github.com/zenstruck/foundry#stories - with these, you could define - using the boring, but readable code that you have at the top of your post, the one with the loop - all of the lookup data you need. And then you can simply execute the story to get everything set up. This is what stories are meant for :) - let me know what you think.

Also I am trying to figure it out how to pass random object per each iteration according their documentation

This is where Foundry gets really interesting, but also a little tricky, as there are subtle ways to do this "relation" stuff and they all have different effects. So, I think what you want is this:

CommentFactory::new()->createMany(10, function() {
    return ['post' => PostFactory::random()];
});

Let me know if that works :). With the original code, PostFactory::random() is executed once, and that ONE object is passed to the createMany() function, which it then uses for all 10 comments. With the callback, the callback is called 10 times, which allows the random() function to be called each time. This is documented, but only in the Many-To-Many section - the ManyToOne probably needs another example :).

Cheers!

Hey quynh-ngan_vu!

Yea, I did see that Faker was recently archived. Fortunately, it's already been rescued! https://github.com/FakerPHP...

Unless something changes dramatically, yes, I'll definitely continue using it :). We're going to update some courses & add some notes to use the new library. For the official Symfony docs, I don't think they mention Faker there, so I don't think there is anything to update.

Cheers!

Hey sciro - I'm the creator of foundry.

To be clear, the code does work as expected and this is only a PHPStorm warning? I'm also using PHPStorm and I don't see this - what version (of PHPStorm) are you on?

The issue is, `self` in this context, refers to `UserFactory` but the `afterInstantiate()` method has a `self` return type which in that context, refers to `\Zenstruck\Foundry\Factory`. So I understand the warning but as far as I'm aware, this is valid PHP (for 7.2+ anyway) which is why I'm asking about your PHPStorm version.

Does removing the `self` return hint remove the warning (this will still be valid code)?

Hey Kevin B.,
I was using 2020.3 EAP when the error was showing. I now changed back to 2020.2.3 and the warning is gone! I just tested to change the PHP language level in the settings, it was on 7.2, even if I put it on 7.3 or 7.4 it still shows the same warning in 2020.3 EAP. With 2020.2.3 everythings works fine, that's so weird. Didn't expect that to happen even with a EAP.

And when I remove the : self the warning stops showing up in 2020.3 EAP too. But I'm just gonna use 2020.2.3 to be safe for now.

Thank you for taking your time to help me! I really like foundry, it's great! :)

Hey Utilisateur

The latest version of Foundry allows defining <a href="https://github.com/zenstruck/foundry#factories-as-services&quot;&gt;&quot;factories as services"</a> so you now can inject the password encoder service into your UserFactory. The example in the docs shows just that.

Ryan's suggestion of pre-encoding the password is still my preferred method but you now have the option. Pre-encoding is <a href="https://github.com/zenstruck/foundry#miscellaneous&quot;&gt;now documented</a> as well (#3 in the linked list).

Hi Kevin B.
Thanks for the heads up; it's always good to know an option is available without requiring workaround.
Cheers!