Got unexpected PRIMITIVES type

[vasily-polonsky]

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

• 1. The issue provides a reproduction available on
  Github,
  Stackblitz
  or
  CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

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:

• OS: macOS ventura
• @graphql-mesh/0.87.8:
• NodeJS: 18.16.1

Additional context

[tlosbar]

Got the same error with these versions in dependencies :
@graphql-mesh/cli: "0.87.8"
@graphql-mesh/openapi: "0.95.5"

So I returned back to :
@graphql-mesh/cli: "0.85.1",
@graphql-mesh/openapi: "0.94.4"

And everything work again ...

[davorjokic-e2x]

Workaround that worked form me is @envelop/graphql-jit plugin.

[ardatan]

Fixed in the latest release!