Here is a link to the current schema. What I don’t understand is that after adding in the @custom directive mutations at the bottom, I am now having issues uploading the schema. I may have made some other change but I’ve primarily been focusing on trying to get these to work. Any guidance on deciphering this error would be great!
Ugh, @core-devs is there anyway to make these error messages more friendly? Being native to MySQL, their error messages are easier to digest at least having a snippet of the query where the problem lies. Maybe instead of “Line 3, Column: 4” You could provide the snippet of schema. This will usually point to the error faster. Most times it is an extra space, colon, unmatching brackets, etc.
@forstmeier, can you provide schema? I understand that is not always possible. I try to keep a working version of my schema in our github so we at least have something to compare against with what changed. Do you have anything like this to know exactly what you changed? If so, can you post at least those parts?
resolving updateGQLSchema failed because input:601: Type Mutation; Field editUser; body template inside @custom directive could not be parsed.
input:607: Type Mutation; Field removeUser; body template inside @custom directive could not be parsed.
This is interesting. Not sure why it would allow your createUser to go through seemingly without error, but error parsing your editUser and removeUser.
This was a long shot, but I actually resolved out why. Not that I think it is correct, but that it is a Dgraph bug/restriction.
Your body for editUser and removeUser both contain this snippet:
I was able to receive a successful parse by using instead:
I believe that numbers are allowable in property names in JSON.
The problem was identified here:
But was should now be resolved as also noted on that same thread: