mirror of
https://github.com/element-hq/element-web
synced 2024-11-27 11:47:23 +03:00
Always insert rooms into lists when they get lost
Room upgrades, direct chats, etc all end up being lost in these scenarios. Instead of losing them to the list, try and put them into a relevant spot of the list. Fixes https://github.com/vector-im/riot-web/issues/9020
This commit is contained in:
parent
1a7c313de7
commit
a34f3780f3
1 changed files with 5 additions and 11 deletions
|
@ -477,20 +477,14 @@ class RoomListStore extends Store {
|
|||
room, category, this._state.lists[key], listsClone[key], lastTimestamp);
|
||||
|
||||
if (!pushedEntry) {
|
||||
// Special case invites: they don't really have timelines and can easily get lost when
|
||||
// the user has multiple pending invites. Pushing them is the least worst option.
|
||||
if (listsClone[key].length === 0 || key === "im.vector.fake.invite") {
|
||||
listsClone[key].push({room, category});
|
||||
insertedIntoTags.push(key);
|
||||
} else {
|
||||
// In theory, this should never happen
|
||||
console.warn(`!! Room ${room.roomId} lost: No position available`);
|
||||
// There's some circumstances where the room doesn't fit anywhere, so just
|
||||
// push the room in. We push it in at the start of the list because the room
|
||||
// is probably important.
|
||||
listsClone[key].splice(0, 0, {room, category});
|
||||
}
|
||||
} else {
|
||||
insertedIntoTags.push(key);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// Double check that we inserted the room in the right places
|
||||
for (const targetTag of targetTags) {
|
||||
|
|
Loading…
Reference in a new issue