CharloMez

Results 30 comments of CharloMez

using "Behatch\Context\RestContext" cause The service has a dependency on a non-existent service "behatch.http_call.request"

I have the same issue. The problem is that behatch and symfony-extension have two way to inject dependencies. You can inject Behatch dependencies through behat.yml like this: ``` - App\Behat\Context\JsonExtendedContext:...

using "Behatch\Context\RestContext" cause The service has a dependency on a non-existent service "behatch.http_call.request"

@pamil I'm trying, but I don't find how to get all ArgumentResolver... when I try in compiler pass ``` use Behat\Behat\Context\ServiceContainer\ContextExtension; ..... $container->findTaggedServiceIds(ContextExtension::ARGUMENT_RESOLVER_TAG); ``` I got nothing, but behat find...

feature(doctrine events): allow factories to disable doctrine events.

@kbond actually I tried to build a docker environment to make tests works in local env, I partially succeed (I can't run functional tests). So it's almost a blind devlopment....

feature(doctrine events): allow factories to disable doctrine events.

I set up a docker environment with php/pqsql/nginx, I configured it well, the DATABASE_URL is well set in the container, but I still don't succeed to run your test suite....

feature(doctrine events): allow factories to disable doctrine events.

ok finally I succeed to make it run locally (with my docker setup), and it works locally with a php8.

feature(doctrine events): allow factories to disable doctrine events.

@kbond finally CI is ok (except scrutinizer, I don't know why, everything look green). I will try to share my docker-compose environment after some cleaning

feature(doctrine events): allow factories to disable doctrine events.

> Just a few comments: > > 1. Relation factory's created during `create()` would currently have events called even if disabled by the parent. There are certain scenarios where they...

feature(doctrine events): allow factories to disable doctrine events.

> FYI, `withoutPersisting` is "passed" down to sub-factory's Ah ok I didn't notice, my bad. But when I said that, I thought more about different way to declare it in...

feature(doctrine events): allow factories to disable doctrine events.

ok let's do it like that (follow the disable to child factories)

feature(doctrine events): allow factories to disable doctrine events.

> Ok, yeah, I'm thinking let's disable events for all of create. The solution for allowing sub-factory's to be created with events will be to create them first: > >...