graphQLSchemaExtension custom GraphQL resolvers not replacing defaults

[dcousens]

export const extendGraphqlSchema = graphQLSchemaExtension<Context>({
  // ...
  resolvers: {
    Mutation: {
      // TODO: this isn't working, it isn't being called, nor is a Post actually deleted
      deletePost: (root, { id }, context) => {
        return context.db.Post.updateOne({
          where: { id },
          data: {
            isDeleted: true
          }
        });
      }
    },
  },
  // ...
})

See working example of the problem in 285b948

[borisno2]

So this looks to be an issue with the mergeSchema in @graphql-tools/schema just here... adding extractedResolvers.push(config.resolvers); to after the for loop pushes the custom GraphQl resolver into the array and it works.

something like this

for (const schema of schemas) {
  extractedTypeDefs.push(schema);
  extractedResolvers.push(utils.getResolversFromSchema(schema));
  extractedSchemaExtensions.push(merge.extractExtensionsFromSchema(schema));
}

extractedResolvers.push(config.resolvers);

return makeExecutableSchema({
        parseOptions: config,
        ...config,
        typeDefs: extractedTypeDefs,
        resolvers: extractedResolvers,
        schemaExtensions: extractedSchemaExtensions,

Looking deeper I have found this Github issue ardatan/graphql-tools#4367 with a PR that has been open for a month, will follow up on that PR.

[borisno2]

New PR in upstream package ardatan/graphql-tools#4455

[borisno2]

Updated PR in upstream package ardatan/graphql-tools#4463

[dcousens]

If we don't have a resolution, could we drop using graphql-tools and write something that works for us?