Testing Modules - Property 'resolvers' does not exist on type GraphQLModule<any, any, any>

[markcdev]

Following the example from the testing documentation and getting an error with the resolvers property not being available on my module. I tried using the selfResolvers property instead and i'm not sure if it's related but my provider isn't being swapped out for the new test one configured in my test module and so it's calling the actual implementation.

[ardatan]

Which version of graphql-modules are you using?

[markcdev]

@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

[tlivings]

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.

[tlivings]

Any updates?

[markcdev]

Any news on this?

[ardatan]

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/core@0.5.0-alpha.778c470a
 - @graphql-modules/di@0.5.0-alpha.778c470a

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

[ardatan]

Fixed in 0.6.5