Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: establish 1on1 mls conversation with new removal key [WPB-10744] #6502
feat: establish 1on1 mls conversation with new removal key [WPB-10744] #6502
Changes from all commits
1e57b90
39108e7
4d19352
ac6fa02
9cfff54
9a57dc2
1fb8cd3
5ab1dec
effb545
bec6335
9e2816e
c124b37
d7306bb
61e6578
23ee59b
b28eca5
c012b0f
6e89c7d
0119cb2
ebad5ca
a1d04b3
a476b1c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the main change, we can register a conversation with a removal key that comes from a different endpoint
Check warning on line 679 in packages/core/src/conversation/ConversationService/ConversationService.ts
GitHub Actions / lint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code block was a previous attempt to solve a related issue without requiring a change to the backend response, by calling the
deleteSubconversation
endpoint instead ofdeleteSubconversationSelf
.see #6434
This is no longer required
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the removal key is provided by the conversation endpoint, we use that one, else, we use a removal key provided by getPublicKey (our own backend removal key)