Allowing mocks for missing keys within provided resolvers

[coreylight]

Hello,
With version 7 we could provide partial data for our resolvers, and the mocking utility would "fill in the blanks" with the respective mocks. Did this change with version 8?

Here's a reproduction of what I'm trying to explain:
https://codesandbox.io/s/graphql-tools-mocking-with-resolver-preservation-inzxf?file=/index.js

See comment in src for wanted behavior. But I am expecting the id key here to be "filled in" by the mock setup.
What am I missing?

[Urigo]

Hi @coreylight , the resolvers you created are resolvers just for mocks, not the actual resolvers you will use with the executable schema in production right?

If the resolvers are your regular resolvers, they should be part of the executable schema.
You passed them into the resolvers of addMocksToSchema which has different objective - they are resolvers specifically for mocking and give you access to a global store for the mocks.

https://codesandbox.io/s/graphql-tools-mocking-with-resolver-preservation-forked-0yxxf?file=/index.js

But, if you are using these resolvers just for the mocking purposes, I think you might hit something that might be not working well.
Can you clarify first?

Thanks

[coreylight]

Thanks for the reply,
My use case is that this server is used solely for integration testing, so there is no "production" 😄
Recapping what I want to do (and what I seem to do in v7)

• Write resolvers for queries that provide all or partial data
• Allow the mock setup to fill in all the missing pieces (ie if the key requested is undefined)

Maybe the issue arises with more complicated scenarios like arrays or nesting?
I made a new test scenario here that passes resolvers to makeExecutableSchema as you mentioned, but changes the signature of the query to return an array - and it seems to be behaving not as I'd like.

[Urigo]

Could you add a text like that in a PR to the repo?