Page MenuHomePhabricator

[lib] add `outboundP2PMessageIDs` to `LocalMessageInfo` to track progress
ClosedPublic

Authored by kamil on Fri, Aug 23, 5:34 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Sep 11, 1:35 PM
Unknown Object (File)
Tue, Sep 10, 4:29 PM
Unknown Object (File)
Mon, Sep 9, 5:08 PM
Unknown Object (File)
Mon, Sep 9, 12:18 PM
Unknown Object (File)
Mon, Sep 9, 10:06 AM
Unknown Object (File)
Mon, Sep 9, 9:54 AM
Unknown Object (File)
Thu, Sep 5, 9:09 PM
Unknown Object (File)
Tue, Sep 3, 2:39 PM
Subscribers

Details

Summary

ENG-8423.

We decided to use the existing store for local messages for two reasons, to avoid adding a new store, and because in components, LocalMessageInfo is easily accessible (I think it saves us at least a couple of days of work).

Additionally LocalMessageInfo seems like a reasonable place to put this data.

All fields in LocalMessageInfo are optional, which means this does not require a migration.

Depends on D13152

Test Plan

Make sure outboundP2PMessageIDs are persisted & read on app start.

Note: This stack is tested end-to-end according to the process described here.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Fri, Aug 23, 7:25 AM
tomek added inline comments.
lib/reducers/message-reducer.js
1664–1675 ↗(On Diff #43610)

It is a bit hacky. We should at least generate a DB op to update the state.

This revision is now accepted and ready to land.Mon, Aug 26, 3:56 AM