Allow modifying attribute values before calling Doctrine's find() method? about foundry HOT 3 OPEN

This is different from https://github.com/wouterj/symfony-demo/blob/fc122b2615652934a66acddfb6cb26241c883235/tests/Command/AddUserCommandTest.php#L108, correct?

from foundry.

My initial vision for Foundry and how I personally use it is as a direct interface to the database row. I'm not opposed to such a feature but feel it might add a lot of complexity. I somewhat resisted "Factories as Services" for the same reason.

In your example above - what about creating 2 constants: DEFAULT_PASSWORD=kitten & DEFAULT_HASHED_PASSWORD=(prehashed kitten) and use these in your tests? This would solve this issue and remove the need for your factory to be a service (it wouldn't need the password encoder). You'd get at least a little speed boost here too (and depending on your config, possibly a substantial speed boost)

from foundry.

This is different from https://github.com/wouterj/symfony-demo/blob/fc122b2615652934a66acddfb6cb26241c883235/tests/Command/AddUserCommandTest.php#L108, correct?

Yes, I guess that's a Doctrine error. If that error is fixed, and this is resolved (I need to think about your 2nd comment), we can remove all custom assertions in that test and rely on assertExists(). This means we no longer have to support #105

from foundry.