olaf
08/09/2017, 7:18 AMpost
, for that it needs to compare the new values against the old to specify what exactly changed.
It works well for scalar fields, but having trouble with relations.
(By the way, am aware that the function itself won’t trigger from a change in the relation, will address that with the Dummy field workaround)
What I have now:
subscription {
Post(filter: {
mutation_in: [CREATED, UPDATED, DELETED]
}) {
updatedFields
node {
id
name
admins {id}
}
previousValues {
id
name
admins: id
}
}
}
So far updatedFields
will give all admins on the post, but previousValues
doesn’t and will not accept the same format. It does give the id of 1 admin when formatted as above.travissperry
08/09/2017, 6:00 PMsamjbmason
08/09/2017, 6:06 PMmj
08/10/2017, 1:11 PMStore error: the application attempted to write an object with no provided id but the store already contains an id of User:cj64seqkwhnb10183rc67zyaj for this object.
lewisblackwood
08/13/2017, 9:30 PMmj
08/14/2017, 1:10 PMnguyendanhson1989
08/15/2017, 4:35 AMauser
08/15/2017, 9:35 PMnguyendanhson1989
08/16/2017, 3:53 AMnguyendanhson1989
08/16/2017, 4:06 AMnguyendanhson1989
08/17/2017, 8:34 AMnguyendanhson1989
08/17/2017, 8:34 AMnguyendanhson1989
08/17/2017, 8:34 AMnguyendanhson1989
08/17/2017, 8:34 AMnguyendanhson1989
08/17/2017, 8:34 AMnguyendanhson1989
08/17/2017, 9:39 AMnguyendanhson1989
08/17/2017, 9:39 AMnguyendanhson1989
08/17/2017, 9:39 AMnguyendanhson1989
08/17/2017, 9:39 AMnguyendanhson1989
08/17/2017, 9:49 AMgeorgelovegrove
08/17/2017, 8:50 PMnguyendanhson1989
08/22/2017, 7:57 AMmartin
09/12/2017, 5:38 PMwojtek
09/20/2017, 4:58 PMnik
09/21/2017, 6:49 PMpeterp
09/22/2017, 4:43 PMtakeshiamano
09/23/2017, 1:52 PMamann
09/26/2017, 7:36 PMdannyql
09/26/2017, 7:56 PMtej
09/27/2017, 3:50 PM