This demo shows how mergeSchemas breaks the recursive nature of resolvers:
if a new field is added that should resolve to an object type, none of that
object type’s pre-existing resolvers will be called. For some reason, the
resolver for the new field is expected to return an object with object-resolved
values for each field.
$ git clone [email protected]:exogen/schema-stitching-bugs.git
$ cd schema-stitching-bugs
$ yarn
$ node 1-makeExecutableSchema.js
$ node 2-addResolverFunctionsToSchema.js
$ node 3-mergeSchemas.js
$ node 4-extendSchema.jsNote that demos 1, 2, and 4 work, but demo 3 does not.
