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 there, I'm using Mesh with the GraphQL source handler and I've discovered that it's incompatible with my endpoint's graphql implementation. Calling that graphql endpoint with extensions set, and not just query/operationName/variables causes the query parser on the server's end to blow up. Given that the endpoint is maintained by a 3rd party, resolving that underlying issue won't be possible for some time.
So my question is: short of rolling my own proxy server, is there a way to prevent GraphQL Mesh from sending extensions out with its queries to graphql endpoints?
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
-
Hi there, I'm using Mesh with the
GraphQL
source handler and I've discovered that it's incompatible with my endpoint's graphql implementation. Calling that graphql endpoint withextensions
set, and not justquery
/operationName
/variables
causes the query parser on the server's end to blow up. Given that the endpoint is maintained by a 3rd party, resolving that underlying issue won't be possible for some time.So my question is: short of rolling my own proxy server, is there a way to prevent GraphQL Mesh from sending
extensions
out with its queries to graphql endpoints?Beta Was this translation helpful? Give feedback.
All reactions