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

Operation Name not forwarded to remote via stitchSchemas #4293

Closed
klippx opened this issue Mar 10, 2022 · 2 comments
Closed

Operation Name not forwarded to remote via stitchSchemas #4293

klippx opened this issue Mar 10, 2022 · 2 comments

Comments

@klippx
Copy link
Contributor

klippx commented Mar 10, 2022

Describe the bug

Operation Name is not forwarded correctly to schema produced by stitchSchemas from import { stitchSchemas } from '@graphql-tools/stitch'

We are using stitchSchemas to wrap several remote graphql services in one BFF and those services need operation name intact.

To Reproduce

I have added a failing test in a branch, but I need to create the issue before opening a PR to view the diff.

Update: PR

Expected behavior

Operation Name provided by client is critical to be forwarded to the underlying remote schemas, especialy if they require operationName in query for metrics purposes.

Environment:

  • OS: macos
  • @graphql-tools/stitch: 8.4.4
  • NodeJS: v14.17.0

Additional context

None

@ardatan
Copy link
Owner

ardatan commented Mar 10, 2022

I think this is duplicate with this one;
#2884

@klippx
Copy link
Contributor Author

klippx commented Mar 10, 2022

Yes, it is the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants