Nicolas PHILIPPE

Bundle config diff: ```diff zenstruck_foundry: - auto_refresh_proxies: null instantiator: - without_constructor: false + use_constructor: true allow_extra_attributes: false always_force_properties: false service: null + orm: + auto_persist: true + reset: + connections:...

lazy value has been implemented since then!

cool! I'm just wondering if in any way, we could add a `->proxy()` method to the `PersistenceObjectFactory`... because it will be one of the only usecase, I'd reallyl need proxies

- [ ] `inverse_one_to_many_relationship_without_cascade()` https://github.com/kbond/foundry-next/pull/12 - [x] fixed by https://github.com/kbond/foundry-next/pull/17 - [x] `one_to_many_with_two_relationships_same_entity()` - [x] `one_to_many_with_two_relationships_same_entity_and_adders()` - [x] `can_use_adder_as_attributes()` - [x] `inverse_many_to_many_with_two_relationships_same_entity()` - [x] `one_to_many_polymorphic_with_nested_collection_relationship()` - [x] `ModelFactoryTest::can_set_state_via_new` => https://github.com/zenstruck/foundry/pull/559...

I'm adding some todo here both of these PRs should be ported in 2.x: - [x] https://github.com/zenstruck/foundry/pull/577 (#587) - [x] https://github.com/zenstruck/foundry/pull/580 - [x] https://github.com/zenstruck/foundry/pull/592 => https://github.com/zenstruck/foundry/pull/600

Hi @cezarpopa that would be very nice to add some linting to the doc (your last PR is actually a proof that this issue is still relevant :innocent:) I'd say...

Hi, thaks for reporting this. It seems that you're using PHPUnit 11. But Foundry still have not taken the phpunit 10 train, nor the whole Symfony world... we are more...

From : https://docs.phpunit.de/en/11.0/annotations.html > PHPUnit will first look for metadata in [attributes](https://docs.phpunit.de/en/11.0/attributes.html#appendixes-attributes) before it looks for annotations in comments. When metadata is found in attributes, metadata in comments is ignored....

Hello, I don't see any problem to add this as a new parameter to `Configuration::repositoryFor()` I'm just wondering something: the `$objectOrClass` here is not enough? does that mean we can...

ok, I just learnt something, I was thinking it was not possible!