Toggling validation on graphql Mesh

[csuriano23]

Hi there,
I have a GraphQL endpoint served through GraphQL Mesh which applies custom logics on validation errors (logging, tracing at database, ...). Is it possible to disable for this source the validation step on GraphQL Mesh, which currently intercepts the invalid requests, preventing the microservice from doing its job?

Thank you

[ardatan]

Could you elaborate with a more clear example? What do you expect and what do you see instead?

[csuriano23]

Let's suppose I have a .meshrc.yaml like this:

sources:
  - name: Countries
    handler:
      graphql: 
        endpoint: https://countries.trevorblades.com/graphql

If I apply a query like:

query {
  continent(code: "EU") {
    code
    countries {
      capital
      name
    }
    name
  }
}

The query is valid, so the query is correctly parsed by Mesh and forwarded to the providing service.

If I write a malformed query, like:

query {
  continent(code: "EU") {
    code
    countries {
      capital
      name
    }
    name
    notExists
  }
}

validation doesn't pass on mesh, so I get the error without the request being forwarded to the business services.
I'd like a way to configure that for a source, also invalid queries are propagated to the business service, so additional tracking steps can be done (write custom logs on database for example)

[dlpx-akashpandey]

I am also stuck in the same situation. I would really appreciate an update on the thread.

[csuriano23]

Thinking about the case, I see this is problematic, since probably validation on generated schema is preparatory to a correct routing between services. Maybe there is a way to catch validation exceptions and apply actions on parsed operation name / resolver