You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm currently migrating out Yoga API to graphql-code-generator from the old graphql-binding tools but have an issue. The new Resolver type is no longer directly callable and our codebase (which is almost as old as graphql-binding!) uses this a lot.
I know that we should refactor our code so that resolvers aren't ever called directly by our code, but that's not something we're able to take on at the moment. Is there an easy way to either tell the code generator to omit ResolverWithResolve, or maybe any TypeScript gurus can help with narrowing the type safely?
I've seen issue #3024 which seems to be the same thing, but it looks like noSchemaStitching has been removed?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm currently migrating out Yoga API to
graphql-code-generatorfrom the oldgraphql-bindingtools but have an issue. The newResolvertype is no longer directly callable and our codebase (which is almost as old as graphql-binding!) uses this a lot.I know that we should refactor our code so that resolvers aren't ever called directly by our code, but that's not something we're able to take on at the moment. Is there an easy way to either tell the code generator to omit
ResolverWithResolve, or maybe any TypeScript gurus can help with narrowing the type safely?I've seen issue #3024 which seems to be the same thing, but it looks like
noSchemaStitchinghas been removed?Beta Was this translation helpful? Give feedback.
All reactions