'Invalid use of comma' error on simple GraphQL get queries

Issues Dgraph
, , ,
10

CosmicPangolin commented :

@MichelDiz @MichaelJCompton

Hey guys, any thoughts here? Beyond this issue, there are a few other ID-related features of the GraphQL API that have felt a bit unnatural in my quest to build a generic repo for handling my data models:

  • The TypePatch object for TypeUpdate mutations doesn’t seem to map ID! or @id fields since they are passed in ‘filter’, which means users must null these fields before locally serializing data models…in my case, I have that firebaseUserId field that I don’t even want to be nullable

  • For TypeUpdate mutations, “filter” on String @id fields requires StringHashObject, when we only need [String] for ID! fields. In general I feel like it would be useful to have some Update mutation examples on the site since that has the most irregular input shape but is only mentioned in passing.

  • Most things I’ve bumped up against have just thrown ‘unknown location’ errors. It’s taken a few rough days of deep schema introspection and trial/error to identify these issues around constructing mutations and serializing data, given nesting and custom IDs.