Page MenuHomePhabricator

[lib] Update `threadStore` with `threadStoreOps` for `updateActivity.success` action
ClosedPublic

Authored by atul on Jun 2 2022, 12:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jul 4, 1:35 AM
Unknown Object (File)
Wed, Jul 3, 7:18 PM
Unknown Object (File)
Wed, Jul 3, 12:17 AM
Unknown Object (File)
Tue, Jul 2, 9:41 AM
Unknown Object (File)
Sat, Jun 29, 4:50 PM
Unknown Object (File)
Thu, Jun 27, 5:12 AM
Unknown Object (File)
Thu, Jun 27, 5:11 AM
Unknown Object (File)
Wed, Jun 26, 7:25 PM

Details

Summary

Copied from D4185:

Previously we were directly updating the threadStore object with the necessary changes for each action... and also constructing a corresponding list of ops that were used for modifying the SQLite store (on native).

We've had an assertThreadStoreThreadsAreEqual check for each action to verify that the threadStore being constructed "directly" and via the "ops approach" were equivalent. At this point we're pretty confident that they are, and so can safely remove some of the redundant code.

In this diff we remove the assertThreadStoreThreadsAreEqual and return the "processed" threadStore as the "updated" threadStore.


Depends on D4190

Test Plan

Hopefully the months of having assertThreadStoreThreadsAreEqual check in are sufficient.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable