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

@graphql does not forward unknown directives to upstream GraphQL servers #2242

Open
amitksingh1490 opened this issue Jun 21, 2024 · 1 comment · May be fixed by #2277
Open

@graphql does not forward unknown directives to upstream GraphQL servers #2242

amitksingh1490 opened this issue Jun 21, 2024 · 1 comment · May be fixed by #2277
Assignees

Comments

@amitksingh1490
Copy link
Collaborator

amitksingh1490 commented Jun 21, 2024

Currently, when using the @graphql directive, directives included in the query are not forwarded to upstream GraphQL servers. This behavior can lead to issues when upstream servers have custom resolvers designed to interpret specific directives, such as @cascade as detailed in the Dgraph documentation.

Expected:

The @graphql handler should forward directives that Tailcall does not recognize to the upstream server. This allows the use of server-specific directives and ensures that custom resolvers on the server can function correctly.

@meskill meskill self-assigned this Jun 21, 2024
@meskill
Copy link
Contributor

meskill commented Jun 23, 2024

Blocked by async-graphql/async-graphql#1547

@meskill meskill linked a pull request Jun 24, 2024 that will close this issue
6 tasks
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

Successfully merging a pull request may close this issue.

2 participants