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

Potential fix for #407 #416

Closed
wants to merge 7 commits into from

Conversation

KammererTob
Copy link
Contributor

Potentially Fixes #407

Checklist

  • Pull requests follows the contribution guide
  • New or modified functionality is covered by tests

Description

This aims to to fix #407 . The problem appears to be caused by the resolver choosing a interface method as the resolver for a field, without checking if there are other resolvers for the same field with a more concrete return type. There are multiple possible issues still left to be adressed i believe:

  1. abstract return types should probably also be pushed to the back of the list
  2. there still can be more concrete return types further back in the list. I am not sure how we could identify which return type is the most concrete

@vojtapol
Copy link
Member

Thanks for the contribution. I am looking into it.

@vojtapol
Copy link
Member

Thank you for investigating this. I have used this PR as an inspiration for the fix here:
647885c

@vojtapol vojtapol closed this Jul 16, 2020
@KammererTob
Copy link
Contributor Author

Perfect. That looks better. Thanks for having a look

@KammererTob KammererTob deleted the #407 branch July 16, 2020 14:55
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 this pull request may close these issues.

[Question] Help with FieldResolverError on classes from external libraries
2 participants