Setting null to delete edges doesn't work - GraphQL Tour Schema site 7

Users Dgraph
1

https://dgraph.io/tour/graphqlschema/7/
the site 7 has a problem

mutation {
  updatePerson(input: {
    filter: { xid: { eq: "alice" } }
    remove: { manages: null }
  }) 
}

that doesn’t work because:

{
  "errors": [
    {
      "message": "Field \"updatePerson\" of type \"UpdatePersonPayload\" must have a selection of subfields. Did you mean \"updatePerson { ... }\"?",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ]
    }
  ]
}

i think that this is maybe because of the “null” type.
How to solve that issue?

Whom can I @ so that he can update that Learn site so others won’t have that problem?

image
image2837×1085 306 KB

2

I’m just trying to reproduce, but you can raise I support ticket following these instructions: Raising a Support Ticket in Dgraph Cloud - YouTube

1 Like
3

this query makes troubles too

@amaster507 these mistakes are also probably a migration problem from the DQL Learn to GraphQL Learn migration, correct?

image
image2119×1007 200 KB

4

I was unable to add the schema to my instance due to this error:

runnable.js:288 TypeError: Cannot read properties of undefined (reading '0')
    at eval (webpack:///./js/runnable.js?:274)
    at Array.forEach (<anonymous>)
    at exports.IncomingMessage.eval (webpack:///./js/runnable.js?:273)
    at exports.IncomingMessage.emit (webpack:///./node_modules/events/events.js?:158)
    at endReadableNT (webpack:///./node_modules/readable-stream/lib/_stream_readable.js?:1010)
    at afterTickTwo (webpack:///./node_modules/process-nextick-args/index.js?:28)
    at Item.run (webpack:///./node_modules/process/browser.js?:153)
    at drainQueue (webpack:///./node_modules/process/browser.js?:123)

Do you see that error in Chrome console, so there’s definitely a problem there. Are you seeing any errors in developer console in browser?

1 Like
5

Unfortunately no error

but I think it’s also a migration error (the graphql tutorial is just a migration from the DQL tutorial), anyway I will start to use ONLY DQL since it makes more sense. graphql is just too limited

image
image2880×1800 530 KB

6

GraphQL is limited and highly typed lang. But the whole hall of tools for the Front-end really worth the shot. You can also use DQL within GraphQL.

1 Like
7

image
Is that not an errror on the form-settings request?

I started out with DQL and it helped me learn to think about my data as a graph. However, I’m curious what are you not able to do with Dgraph’s graphql API? The only thing I’ve needed DQL for so far is transactions (when there are multiple mutations that depend on each other) or creating custom graphql resolvers.

1 Like
8

that was previous. its already gone now. really weird why it doesn’t work. i just followed the tutorial along

https://dgraph.io/tour/graphqlschema/7/#

image
image2880×1800 509 KB

9

I recommend just running the Dgraph standalone instance on your machine and then executing queries with a graphql client like Altair https://altair.sirmuel.design/

https://dgraph.io/downloads/

1 Like