Testing Modules - Property 'resolvers' does not exist on type GraphQLModule<any, any, any> about graphql-modules HOT 7 CLOSED

Same problem. The overwrite: true for provider doesn't seem to do anything.

Also, in the example it seems like the useValue is providing an override to the resolvers name as opposed to provider's function name. I'd expect the latter considering it is an override on provider?

In general, this doesn't seem like "injecting" a mock provider into the module. This is mentioned in the dependency injection section specifically referring to tests but remains unclear.

from graphql-modules.

Which version of graphql-modules are you using?

from graphql-modules.

@ardatan I downgraded from 0.3.0 to 0.2.18 and I can see the property now. However it still isn't switching out the implementation for the mock

from graphql-modules.

Any updates?

from graphql-modules.

Any news on this?

from graphql-modules.

The bug is related to overwriting an existing provider by using;

injector.provide({
   provide: ExistingProvider,
   overwrite: true,
   useClass: MockProvider
})

I created a PR for this issue, and published an alpha release;

- @graphql-modules/[email protected]
 - @graphql-modules/[email protected]

So, could you try testing your module again with this alpha version?
Please read the updated documentation before doing that;
https://github.com/Urigo/graphql-modules/blob/test-modules/docs/introduction/test-your-module.md

from graphql-modules.

Fixed in 0.6.5

from graphql-modules.