-
Hi, I just stumbled upon this error:
but I can't really make anything out of it, nor do I know where to look for errors. Is it an issue with the resolvers, or with the typedefs? The strange thing out it is that it only occurs on our deployed infrastructure, and never on my local development environment. In the meantime I bumped some dependencies, including the We recently implemented caching via directives. I don't know if that might have anything with how the schema is assembled. Some ContextThe versions used:
Our schema is generated using
Our resolvers generally look like this:
Our typedefs look like this:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Could you create a live reproduction on CodeSandbox? |
Beta Was this translation helpful? Give feedback.
-
Just found the issue. We were manually overriding the version of |
Beta Was this translation helpful? Give feedback.
Just found the issue. We were manually overriding the version of
graphql
in our package.json, so it had nothing to do with this package. Sorry for the inconvenience!