Introduce the subconversation types and change federation message sending request types #2925
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zebot
added
the
ok-to-test
elland
approved these changes
Dec 13, 2022
smatting
approved these changes
Dec 13, 2022
- It doesn't belong to this PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is in preparation for https://wearezeta.atlassian.net/browse/FS-901, i.e., for introducing endpoints for MLS subconversations.
The PR introduces subconversation types, which affect the federation API for MLS message sending requests as eventually we want to be able to use subconversations on remote backends. Note that the PR does not introduce any subconversation functionality; it just introduces needed types.
This is a federation API breaking change.
Checklist
changelog.d