-
Notifications
You must be signed in to change notification settings - Fork 10.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: webclient still showing DM messages that had already been deleted from the server #31537
Conversation
…d from the server
🦋 Changeset detectedLatest commit: 6a3fc84 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #31537 +/- ##
===========================================
- Coverage 49.57% 49.54% -0.03%
===========================================
Files 3328 3328
Lines 81793 81771 -22
Branches 16881 16877 -4
===========================================
- Hits 40546 40511 -35
- Misses 36503 36514 +11
- Partials 4744 4746 +2
Flags with carried forward coverage won't be shown. Click here to find out more. |
Proposed changes (including videos or screenshots)
Issue(s)
When a room is deleted in the server, the webclient does not clear its cache of that room's history.
If a new room is created with the same ID as the deleted room, the client would still show those cached messages from the deleted room in the new room - it also failed to properly send and load new messages to this new room until the user refreshed the window.
This is only possible on basic DMs, where the room id is not random but calculated based on the ids of the users involved.
Steps to test or reproduce
Further comments