-
Notifications
You must be signed in to change notification settings - Fork 390
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
Custom query resolver is always null #12
Comments
@4F2E4A2E Okay... So you're doing wrong the entire resolver.
You should do this:
|
I did ghave tried this before, it dit not work. Did you get this working for sure? |
Yes. The |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Ho can the query method be passed to the right Query type parent?
Or how can the resolver class be annotated correctly in order to resolve?
.graphql
CustomResolver
create schema
result
maybe relevant dependencies
A) What am I doing wrong?
B) Can anyone confirm that custom query types are not supported at the moment?
C) Would a PR supporting this via annotation be welcomed?
The text was updated successfully, but these errors were encountered: