ENG-5307 : Start performing message store ops on worker
ENG-5806 : Start performing message store threads ops on worker
Part of ENG-3490 : Migrate stores to SQLite on web
Start persting messageStore on web, inside of sqlite db.
Depends on D11538
Details
Details
- Reviewers
kamil marcin - Commits
- rCOMM22f31403e96a: [web] Persist messageStore in db
- Open web app, check that the "migration" runs and:
- Ops with messageStore from keyserver are dispatched to the db
- Redux contains the data
- Reload the web app and check that:
- Keyserver doesn't send the message info
- Message info is loaded from db and dispatched in setInitialReduxState action
- Play around with the app check if there are any errors
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Noticed an issue where the message sometimes wouldn't send. It turns out that's because we don't persist nextLocalID on web. So after reloading the webapp new messages had local ids starting from 0, and mesasge reducer started ignoring them.
For now, I've added nextLocalID to persistWhitelist. @inka will be working on changing the local ids to uuids instead of consecutive numbers. These should be pretty fast changes so if they are landed first, I will just remove the additino to whitelist before landing. If I will have to land my stack first than this should just be 1. Remove entry in whitelist 2. Add a redux migration that removes nextLocalID from persisted data (this will need to be done on native anyway).
Comment Actions
Like in previous diff, realized that user infos are used by navinfo in redux state responder so separated the new promise.
This will need a major refactor anyway in ENG-5179 : Handle initial state for multiple keyservers.
Comment Actions
D11552 was landed so removed the change that persisted the nextLocalID as it's now a random uuid and there won't be conflicts after app reload.