You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.
In some of our types (e.g. Annotation) we want to know when the annotation was made, and if it was changed, when it was changed.
To store this, we have 2 fields, created and modified.
There are 2 ways we can fill these fields. One is to require the client to set them (we can make created required in this case). A problem here is that modified would have to be non-required (and only set when an item is Updated?). Also, it means that a client could change created by sending an Updated mutation.
The other option is to make the CE automatically set the created field on a Create mutation, and set modified on an Update mutation. We would have to decide which types we want this behaviour on. Can we think of a situation when we might want to override this behaviour when creating an object?
The text was updated successfully, but these errors were encountered:
In some of our types (e.g. Annotation) we want to know when the annotation was made, and if it was changed, when it was changed.
To store this, we have 2 fields, created and modified.
There are 2 ways we can fill these fields. One is to require the client to set them (we can make created required in this case). A problem here is that modified would have to be non-required (and only set when an item is Updated?). Also, it means that a client could change created by sending an Updated mutation.
The other option is to make the CE automatically set the created field on a Create mutation, and set modified on an Update mutation. We would have to decide which types we want this behaviour on. Can we think of a situation when we might want to override this behaviour when creating an object?
The text was updated successfully, but these errors were encountered: