Page MenuHomePhabricator

[lib] Create a new redux field to store the operations
ClosedPublic

Authored by tomek on Jul 30 2024, 2:47 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 7, 3:37 PM
Unknown Object (File)
Sun, Oct 6, 7:59 PM
Unknown Object (File)
Sun, Oct 6, 7:59 PM
Unknown Object (File)
Sun, Oct 6, 7:28 PM
Unknown Object (File)
Sep 16 2024, 12:10 PM
Unknown Object (File)
Sep 15 2024, 5:55 AM
Unknown Object (File)
Sep 10 2024, 8:09 AM
Unknown Object (File)
Sep 7 2024, 1:43 PM
Subscribers

Details

Summary

When an operation can't be applied, we will store it in this queue.

https://linear.app/comm/issue/ENG-8764/create-a-new-redux-field-to-store-the-updates

Depends on D12921

Test Plan

Run the migrations and check if the store was created.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

tomek requested review of this revision.Jul 30 2024, 3:23 AM
inka added inline comments.
web/redux/persist-constants.js
6 ↗(On Diff #42932)

Shouldn't the store versions match between platforms?

This revision is now accepted and ready to land.Jul 31 2024, 2:52 AM
web/redux/persist-constants.js
6 ↗(On Diff #42932)

We're not there yet. At this point, the mismatch between versions doesn't matter. After we start supporting the backup, maintaining a parity between versions will become critical.

ashoat added inline comments.
web/redux/persist-constants.js
6 ↗(On Diff #42932)

Why not maintain this now? It seems weird that we started supporting it, but now are backtracking it

(I guess it was broken by @atul's migration)

web/redux/persist-constants.js
6 ↗(On Diff #42932)

From the code point of view, it doesn't matter. But we can do that as a good practice - going to update the diff.