Is it safe to assume that the way to do this in the mean time is with custom mutations?
https://graphql.dgraph.io/custom/mutation
Dgraph generates an
addPost
mutation from those types, but we want to do something extra. We don’t want theauthor
to come in with the mutation, that should get filled in from the JWT of the logged in user. Also, thedatePublished
shouldn’t be in the input; it should be set as the current time at point of mutation. Maybe we also have some community guidelines about what might constitute an offensivetitle
ortext
in a post. Maybe users can only post if they have enough community credit.We’ll need custom code to do all that, so we can write a custom function that takes in only the title and text of the new post. Internally, it can check that the title and text satisfy the guidelines and that this user has enough credit to make a post. If those checks pass, it then builds a full post object by adding the current time as the
datePublished
and adding theauthor
from the JWT information it gets from the forward header. It can then call theaddPost
mutation constructed by Dgraph to add the post into Dgraph and returns the resulting post as its GraphQL output.