-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Got unexpected PRIMITIVES type #6003
Comments
Got the same error with these versions in dependencies : So I returned back to : And everything work again ... |
Workaround that worked form me is @envelop/graphql-jit plugin. |
Fixed in the latest release! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue workflow progress
Progress of the issue based on the
Contributor Workflow
Github,
Stackblitz
or
CodeSandbox
Describe the bug
Hi there,
I upgraded versions of
@graphql-mesh/cli 0.85.1-> 0.87.8
@graphql-mesh/graphql 0.94.4-> 0.95.2
I am using mesh for federated subgraphs with custom scalars, each subgraph works as before, but in mesh I started to receive errors "Got unexpected PRIMITIVES type: CUSTOM_SCALAR".
Looks like it is related to zalando-incubator/graphql-jit#216
The thing is that I don't want to replicate scalar implementation in mesh, and want just to forward a request to subgraph and return the result. Or this is the expected outcome and my way of thinking is wrong?
Expected behavior
Environment:
@graphql-mesh/0.87.8
:Additional context
The text was updated successfully, but these errors were encountered: