We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Progress of the issue based on the Contributor Workflow
Make sure to fork this template and run yarn generate in the terminal. Please make sure the GraphQL Tools package versions under package.json matches yours.
Make sure to fork this template and run yarn generate in the terminal.
yarn generate
Please make sure the GraphQL Tools package versions under package.json matches yours.
package.json
Describe the bug
When using an executor combined with delegateToSchema and stitchSchemas, aliasing fields returns null instead of the aliased value
To Reproduce Steps to reproduce the behavior:
Run npm start here: https://stackblitz.com/edit/node-qhocq7?file=index.ts
Expected behavior
Both versions should behave the same
Environment:
The text was updated successfully, but these errors were encountered:
We are having the same issue, Does anyone have a solution?
Sorry, something went wrong.
I don't think this is a bug. In your executor, you don't respect the incoming execution request in your fake response. I've added console.log there.
console.log
No branches or pull requests
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
When using an executor combined with delegateToSchema and stitchSchemas, aliasing fields returns null instead of the aliased value
To Reproduce
Steps to reproduce the behavior:
Run npm start here: https://stackblitz.com/edit/node-qhocq7?file=index.ts
Expected behavior
Both versions should behave the same
Environment:
"@graphql-tools/mock": "^8.7.18",
"@graphql-tools/schema": "^9.0.16",
"@graphql-tools/stitch": "^8.7.40",
The text was updated successfully, but these errors were encountered: