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

Nested interfaces not calling resolvers #6204

Closed
2 of 4 tasks
xharkonen opened this issue May 21, 2024 · 3 comments
Closed
2 of 4 tasks

Nested interfaces not calling resolvers #6204

xharkonen opened this issue May 21, 2024 · 3 comments

Comments

@xharkonen
Copy link

xharkonen commented May 21, 2024

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

  • 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox

    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.

  • 2. A failing test has been provided
  • 3. A local solution has been provided
  • 4. A pull request is pending review

Describe the bug

Having nested interfaces the resolver of the 2nd level is never being matched/called to resolve the field.

To Reproduce Steps to reproduce the behavior:

There's a failing test on the branch https://github.com/xharkonen/graphql-tools/tree/nested-interfaces-issue

Expected behavior

Nested interfaces should be merged and resolve.

Environment:

  • OS:
  • @graphql-tools/...:
  • NodeJS:

Additional context

@ardatan
Copy link
Owner

ardatan commented May 21, 2024

Thanks for creating the issue and the branch. Could you create a PR for that branch?

@xharkonen
Copy link
Author

xharkonen commented May 21, 2024

I forked the repo. Shall I create a PR on the main repo? there's already a PR on the fork.

@ardatan
Copy link
Owner

ardatan commented May 21, 2024

master...xharkonen:graphql-tools:nested-interfaces-issue
Yes you should create a PR on this repo. You can use the link above.

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