Closed
Bug 925048
Opened 11 years ago
Closed 11 years ago
MakeAPI isn't setting updatedAt attribute when creating a new make
Categories
(Webmaker Graveyard :: MakeAPI, defect)
Webmaker Graveyard
MakeAPI
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jon, Assigned: cade)
References
Details
Attachments
(1 file)
Currently the MakeAPI isn't setting the updatedAt attribute when creating a new make. The offending line of code is https://github.com/mozilla/MakeAPI/blob/master/routes/make.js#L55-L60 . We'll also need to write a migration script that sets the updatedAt attribute if it doesn't exist.
|
Assignee | |
Comment 1•11 years ago
|
||
Attachment #815033 -
Flags: review?(jon)
|
Reporter | |
Updated•11 years ago
|
Attachment #815033 -
Flags: review?(jon) → review+
|
||
Comment 2•11 years ago
|
||
Commit pushed to master at https://github.com/mozilla/MakeAPI https://github.com/mozilla/MakeAPI/commit/ca3a10ac41bb06f0a2a78117c52d6a9c74d3b477 Fix Bug 925048 - set updatedAt on creation, add migration to update makes with a null updatedAt (set to createdAt)
|
|
||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
Attachment mime type: text/plain → text/x-github-pull-request
|
|
Reporter | |
Comment 3•11 years ago
|
||
We needed to run a manual ES sync after running the migration script to have the updated sorting work properly.
You need to log in
before you can comment on or make changes to this bug.
Description
•