Improve storage service migration to new field understanding

This commit is contained in:
Scott Nonnenberg 2022-01-26 15:39:25 -08:00 committed by GitHub
parent f9440bf594
commit 2603d53891
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 17 additions and 7 deletions

View file

@ -21,6 +21,7 @@ import { Address } from './types/Address';
import { QualifiedAddress } from './types/QualifiedAddress';
import * as log from './logging/log';
import { sleep } from './util/sleep';
import { isNotNil } from './util/isNotNil';
const MAX_MESSAGE_BODY_LENGTH = 64 * 1024;
@ -789,9 +790,11 @@ export class ConversationController {
// If it's scoped to a given conversation, it's easy to trigger('change'). There are
// important values in storage and the storage service which change rendering pretty
// radically, so this function is necessary to force regeneration of props.
async forceRerender(): Promise<void> {
async forceRerender(identifiers?: Array<string>): Promise<void> {
let count = 0;
const conversations = this._conversations.models.slice();
const conversations = identifiers
? identifiers.map(identifier => this.get(identifier)).filter(isNotNil)
: this._conversations.models.slice();
log.info(
`forceRerender: Starting to loop through ${conversations.length} conversations`
);