Skip to content
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

Integration of AS4 with graphql-jit not working #7774

Closed
hiteshbal91dp opened this issue Oct 31, 2023 · 3 comments
Closed

Integration of AS4 with graphql-jit not working #7774

hiteshbal91dp opened this issue Oct 31, 2023 · 3 comments

Comments

@hiteshbal91dp
Copy link

Issue Description

We are migrating from AS3 to AS4 along with graphql-jit which we used to work with AS3 via executor option of ApolloServer().

According to migration guide we have to move to gateway parameter instead of executor which we did using GatewayInterface definition.

Now, we are facing an issue like consider query where we need to pass mandatory variable as input for mutation, earlier(AS3+graphql-jit+executor) upon not providing mandatory variable in GQL request it was throwing valid error saying $variable should not be null. And now with new implementation we are not getting any such error instead we are getting following.

{
  "data": {},
  "errors": [
    {
      "message": "Internal server error",
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ]
}

Upon debugging we identified that with new graphql-jit implementation via gateway option, compliedQuery is resulting into an error during execution but that error is getting suppressed.

Please let me know if there is any resolution to the above problem.

Link to Reproduction

https://codesandbox.io/p/sandbox/funny-haibt-s4r82s?file=%2Fsrc%2Findex.ts%3A34%2C14

Reproduction Steps

No response

@glasser
Copy link
Member

glasser commented Oct 31, 2023

Is this a different issue from #7773?

@hiteshbal91dp
Copy link
Author

Got it @glasser it seems to be same issue.

Copy link
Contributor

github-actions bot commented Dec 2, 2023

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants