Query sever timestamps in GraphQL?

[maaft]

Thank you for this well thought out push for server-side timestamps!

@amaster507

When an edge is created/removed that utilizes the @hasInverse directive, then both nodes on either side are updated with the _updatedAt predicate with the equivalent of new Date().

I love this. Would help a lot with getting only newest data and not receiving old data from sub-graphs over and over again.

@amaster507

If a user needed to manually set or update the _createdAt or _updatedAt I believe it should be allowed through DQL only

Does this need to be so strict? Why not allow both? For instance, we would definitely need mutable timestamps for client ↔ server synchronization.

When implemented like this, you could choose to allow it or not:

type TimestampConfig {
   active: Boolean!
   mutable: Boolean!
}
@timestamps( createdAt: TimestampConfig, updatedAt: TimestampConfig )