This function should be used during migrations. An example is described in the test plan.
Depends on D14457
Details
Details
- Reviewers
kamil bartek - Commits
- rCOMM4ea52ae68c18: [lib] Create a migration function
Tested the whole stack on both native and web:
- Run the app on Redux version 86 with a modification to processDMOperation making all the INBOUND messages unsupported
- On one platform created a thread and sent a text message. These were visible on the sender, and invisible on the recipient
- Closed the recipient and added a migration that unshimms the thread creation operations, e.g.
unshimDMOperations( state, dmOperationTypes.CREATE_THREAD, handleReduxMigrationFailure, ): MigrationFunction<WebNavInfo, AppState>),
- Run the recipient and noticed the thread appearing
- Added another migration, this time unshimming text messages
- Run the recipient and noticed messages appearing
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| lib/shared/unshim-utils.js | ||
|---|---|---|
| 70 ↗ | (On Diff #47450) | I don't see a reason for this to be optional. If I recall correctly, it was optionall in e.g. unshimClientDB because we wanted to handle both new migration and migrations before handleMigrationFailure was implemented. |
| 107 ↗ | (On Diff #47450) | there is no cookie in the state, each keyserver from KeyserverStore should have its own cookie |