Zied Hamdi

Hi Craig, Sorry for me not anwsering, I missed the notification for your previous answer. I forgot the context in which I had that error, I somehow managed to get...

 As you can see from the image, I don't know what you pass me in the `next` variable, and I can't know which code will execute. Stepping into it...

I added the following code to addQueryFields defined above: ``` const oldResolve = queryResolver.resolve queryResolver.resolve = async (resolveParams) => { console.log( "############ resolve params :", resolveParams ) console.log( "############ resolver:",...

Ok I found it!!! The resolver is not modified, but a new one is created at the call of `addFilterArg` changing the code ``` const queryResolver = ComplaintActionTC.getResolver(resolverName); queryResolver.addFilterArg({ ```...

Ok, so there's maybe an error in the sequence of calls, the weired thing is that it was working with 5.x versions, it stopped as soon as I updated my...

Sorry for the delay, I had to stop the devs for a week This is what yarn list returns: yarn list v1.13.0 ├─ [email protected] ├─ [email protected] ├─ [email protected] └─ [email protected]

If I remove all dependencies leaving only "graphql-compose-mongoose": "latest" By reinstalling dependencies I see there are warnings : warning " > [email protected]" has unmet peer dependency "graphql-compose@>=7.0.1". warning "graphql-compose-mongoose >...

With the dependency config listed above, I isolated the code so that it checks if the field was added immediately after adding it, and yet it doesn't find it ├─...

Please notice when I compare my code with your tests, I don't have the param: filterTypeNameFallback. Is it a necessaty field? anyway I think that if the operation of addFilterArg...

Hi, I cloned g-c and modified the test you pointed me to as follows _(I had to add filterTypeNameFallback: 'Toto' to get it pass)_: ``` describe('addFilterArg', () => { it('should...