Skip to content
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

feat: clear mls group on conversation delete [FS-1602] #14772

Merged
merged 1 commit into from
Mar 3, 2023

Conversation

PatrykBuniX
Copy link
Contributor

@PatrykBuniX PatrykBuniX commented Mar 3, 2023

TaskFS-1602 [Web] Wipe local MLS group when a conversation gets deleted

Clearing local MLS group after deleting a conversation was never implemented (It was handled on-leave only). This PR makes sure that after deleting conversation locally from the store we also wipe MLS group (corecrypto.wipeConversation)

Copy link
Contributor

@przemvs przemvs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥

@codecov
Copy link

codecov bot commented Mar 3, 2023

Codecov Report

Merging #14772 (e4245c5) into dev (af99448) will decrease coverage by 0.01%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##              dev   #14772      +/-   ##
==========================================
- Coverage   42.86%   42.86%   -0.01%     
==========================================
  Files         621      621              
  Lines       21206    21210       +4     
  Branches     4865     4867       +2     
==========================================
  Hits         9091     9091              
- Misses      10959    10963       +4     
  Partials     1156     1156              

@PatrykBuniX PatrykBuniX merged commit a505604 into dev Mar 3, 2023
@PatrykBuniX PatrykBuniX deleted the feat/wipe-mls-group-on-conversation-delete branch March 3, 2023 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants