This is not the Dgraph way as GraphQL is in the Dgraph core as a set of resolvers/rewriters. So yes it is a problem with the GraphQL API endpoint that does not exist on the DQL endpoint, but it is very much still in the hands of Dgraph as I do not host my own GraphQL API on top of DQL like every other GraphQL API in existence. This is why I love Dgraph! But if I have to fight this hard to get simple bugs even recognized then who knows… all my eggs are in one basket here and I am trusting this basket to Dgraph engineers to fix bugs I cannot (wish I knew golang). Please don’t make me look for a new basket as there is nothing even close in comparison.
1 Like