New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix create/update timestamp issues in GraphQL and REST #1847
Conversation
81a1ccd
to
5850cda
Compare
Codecov Report
@@ Coverage Diff @@
## master #1847 +/- ##
==========================================
+ Coverage 65.98% 66.06% +0.08%
==========================================
Files 411 411
Lines 30895 30915 +20
==========================================
+ Hits 20386 20425 +39
+ Misses 8716 8691 -25
- Partials 1793 1799 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
// otherwise it is lost. This is because `class` is unmarshaled | ||
// directly from the request body, therefore `CreationTimeUnix` | ||
// inherits the zero value. | ||
class.CreationTimeUnix = originalObject.Created |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this comment. The perfect level of information about why we do this.
Just pushed some some tests to |
Documentation will need to be updated on the GraphQL Additional Properties reference page |
09a7f17
to
01a8262
Compare
Changes
Set the original creation timestamp before call to put, otherwise it is lost. This is because
class
is unmarshaled directly from the request body, thereforeCreationTimeUnix
inherits the zero value.Add
creationTimeUnix
andlastUpdateTimeUnix
fields toGet
graphql query asString
'sWrite tests to assert both
1.
and2.
Fixes #1844