Report a Dgraph Bug Error Message: “__typename was not executed because no suitable resolver could be found - this indicates a resolver or validation bug. Please let us know by filing an issue.” this error message occurs if one tries to include __typename under mutation. What version of Dgraph are…

Hi @noobloser @tvvignesh , fix for this issue is merged in the master branch. PR: fix(GraphQL): This PR allow to use __typename in mutation. by JatinDevDG · Pull Request #7285 · dgraph-io/dgraph · GitHub

[Bug] upmost __typename in mutation finds no resolver

Issues GraphQL

JatinDevDG (Jatin Dev ) December 21, 2020, 7:52am 2

Hi @noobloser, this behavior is not allowed. You can’t query __typename or anything on type mutation.

Topic		Replies	Views
Upmost __typename in query: Operation not allowed Dgraph Cloud dgraph , kind:bug	4	963	July 25, 2022
GraphQL __typename response on mutations differs in some cases Users	3	517	April 11, 2020
Custom DQL __typename bug / strange behaviour GraphQL	2	640	August 11, 2020
Dgraph returns empty string for __typename when coupled with aggregate edge GraphQL status:accepted , kind:bug , ticket:created	6	783	April 14, 2021
What does __typename do in GraphQL? GraphQL graphql , kind:question , auth	7	6186	September 30, 2020

[Bug] upmost __typename in mutation finds no resolver

Related topics