Page MenuHomePhabricator

[lib] Introduce thread timestamps on the JS side
ClosedPublic

Authored by tomek on Fri, Aug 30, 9:07 AM.
Tags
None
Referenced Files
F2707110: D13214.id43827.diff
Sun, Sep 15, 10:15 AM
F2703502: D13214.id43820.diff
Sun, Sep 15, 2:14 AM
Unknown Object (File)
Sat, Sep 14, 11:53 PM
Unknown Object (File)
Sat, Sep 14, 12:51 PM
Unknown Object (File)
Sat, Sep 14, 11:51 AM
Unknown Object (File)
Wed, Sep 11, 8:14 AM
Unknown Object (File)
Tue, Sep 10, 8:20 PM
Unknown Object (File)
Mon, Sep 9, 6:46 PM
Subscribers

Details

Summary

Create a new property with the timestamps. All the new thick threads will have it. We don't really need to have a migration introducing them, because all the thick threads we have were created by code on dev environments.

https://linear.app/comm/issue/ENG-8751/add-a-timestamps-property-to-a-thick-thread-info

Depends on D13211

Test Plan

On native and web, create a new thick thread, check if it contains the timestamps. Restart the apps and check if the timestamps are still there.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Remove replies count timestamp - the replies count is based on the messages which means it doesn't need a timestamp.

tomek requested review of this revision.Fri, Aug 30, 9:47 AM
This revision is now accepted and ready to land.Tue, Sep 3, 3:06 AM
lib/types/thread-types.js
152 ↗(On Diff #43827)

What is this representing?

lib/types/thread-types.js
152 ↗(On Diff #43827)

It represents the last change of the unread status.