Nicolas PHILIPPE comments

Results 319 comments of


                                            Nicolas PHILIPPE

Add Faker `optional()` by default for nullable fields

maybe `str_replace()` on `{faker}->text({length})`? In this class you can know if the field is nullable from doctrine's metadata be careful, you'd need to modify `ObjectDefaultPropertiesGuesser` as well

Calling setters with more than one argument?

I would indeed use a hook for this. The requested behavior is currently not possible, and I think it could be complex to implement, since we use Symfony's property accessor...

Calling setters with more than one argument?

I'm closing this since it's a stale issue, and I don't think we will ever support this (beside of using a post instantiate hook)

support "in-memory" repositories

cool :) Actually all the code is almost ready :smile: (just need to fix phpstan...)

feat: support `doctrine/orm` 3

won't it be a PITA to maintain tests for both versions?

feat: support `doctrine/orm` 3

closed in favor of https://github.com/zenstruck/foundry/pull/569

It is better that \App\Factory\UserFactory::getDefaults return an entity object.

my 2 cents here: while I think it could be a good idea, I don't see how we could have the same nice DX we have today in Foundry with...

It is better that \App\Factory\UserFactory::getDefaults return an entity object.

I don't think we want to support this

Support for nested property paths

hey @NorthBlue333 I'm wondering if this problem could not be fixed using: ```php class CommentFactory { public function withUserAndPosts(): static { return $this->with(['user' => UserFactory::new(['posts' => PostFactory::new()->many(5))]); // OR return...

Invalid schema name with custom Postgres schema on database reset

Hello @BernardA if the migrations work well in test, couldn't you add the two queries you need inside a migration?