Current workaround (add as any
):
const server = new GraphQLServer({
typeDefs: './src/schema.graphql',
resolvers: resolvers as any,
context: { data },
})
My current understanding is that this is a limitation in graphql-tools
. We should open an issue there.
any workaround until it is fixed?
See comment from above:
Current workaround (add as any
):
const server = new GraphQLServer({
typeDefs: './src/schema.graphql',
resolvers: resolvers as any,
context: { data },
})
Same problem here
I am using makeExecutableSchema.
For me the incompatibility with IResolvers was caused by a missing index signature. All generated resolvers should have it. As a workaround, I declare my resolvers as "...Resolvers.Type & { [key: string]: any } ".
Duplicate of #15
And as stated here I don’t believe it’s a bug with graphqlgen
https://github.com/prisma/graphqlgen/issues/15#issuecomment-461024244
Most helpful comment
See comment from above:
Current workaround (add
as any
):