You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"bundleless" usage should not require doctrine (there is presently an error when requiring foundry without doctrine) - the factories would automatically be with withoutPersisting() behavior
we need to keep the ability to add global state in
We do but I wonder if this could be configured?
zenstruck_foundry:
global_state:
- invokable.service # just a service with ::invoke()
- App\Stories\StoryThatIsAService
- App\Stories\GlobalStory # if not a service, just run GlobalStory::load()
- ...
Then global state could be used in your dev environment when loading fixtures. Stories as services could now be used as global state too.
If this can be done, maybe we can deprecate TestState::addGlobalState() too.
Based on #110 and #311 (comment) we would like to remove "bundleless" usage.
Here are some thoughts:
FOUNDRY_RESET_CONNECTIONS
orFOUNDRY_RESET_OBJECT_MANAGERS
should be passed as config [feat] [remove bundleless usge] use config instead of environment variables #320FOUNDRY_RESET_ODM_OBJECT_MANAGERS
[feat] [remove bundleless usge] use config instead of environment variables #320withoutPersisting()
behaviorThe text was updated successfully, but these errors were encountered: